repowise-dev/claude-code-prompts · Archived

coding-agent-standards

Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.

First seen May 2, 2026

Installation

$ npx skills add repowise-dev/claude-code-prompts --skill coding-agent-standards

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from repowise-dev/claude-code-prompts.

npx skills add repowise-dev/claude-code-prompts

Browse all from repowise-dev/claude-code-prompts

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.1K
License LICENSE
Default branch master
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,183 B
  • docs SUMMARY.md 208 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Coding Agent Standards

Purpose

Use this skill to keep code changes predictable, reviewable, and safe.

Default Behavior

  1. Clarify the requested outcome and constraints before editing.
  2. Prefer small, focused changes over broad refactors.
  3. Preserve existing behavior unless a behavior change is requested.
  4. Keep naming, structure, and style consistent with nearby code.
  5. Add or update tests when behavior changes.

Implementation Checklist

  • Confirm the smallest viable file set to edit.
  • Handle edge cases and explicit failure paths.
  • Avoid speculative abstractions and dead code.
  • Add concise comments only where intent is not obvious.
  • Run available validation steps before finalizing.

Delivery Format

When reporting completion:

  • What changed (files and intent).
  • Why it changed (problem solved or risk reduced).
  • How it was verified (tests, checks, or manual validation).
  • Remaining risks, assumptions, or follow-ups.