coding-agent-standards
Defines practical standards for implementation-focused coding agents.
Skill by repowise-dev
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/repowise-dev-coding-agent-standards
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/coding-agent-standards
What's inside
- Skill name
coding-agent-standards- Description
- Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.
- License
- MIT
- Instructions
- 27 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# 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.
From repowise-dev/claude-code-prompts, MIT.
More from repowise-dev/claude-code-prompts
Signals
- Stars
- 1,217
- Forks
- 399
- Open issues
- 0
- Last commit (this folder)
- Apr 1, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from repowise-dev
- 0.899score

Repowise
repowise-dev
Know what your change breaks before you push.
PluginAFreshness: A★ 7.9KVS Code +3 - 0.645score
prompt-architect
repowise-dev
Designs clear, testable prompts for agent workflows.
SkillDFreshness: D★ 1.2KClaude Code +9 - 0.645score
verification-agent
repowise-dev
Provides a structured verification workflow for code and prompt outputs.
SkillDFreshness: D★ 1.2KClaude Code +9
Cite this page
coding-agent-standards skill. Agent Mart. https://agentmart.dev/skills/repowise-dev-coding-agent-standards (last updated 2026-10-24)