Skip to content
Back to skills

Coding Agent Standards

ASecurity

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

  • 1,200 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-ai

Security analysis

A100/100

Scanned May 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Coding Agent Standards?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coding Agent Standards
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/repowise-dev-coding-agent-standards/badge)](https://www.skillsdirectory.com/skills/repowise-dev-coding-agent-standards)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.
---

# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.