Individual skill
code-standards
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
skills/code-standards/SKILL.md
Source commit 1be9984bdafbb68eaff400bdd82773a1d41ee7ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 228
- Repository last updated
- Aug 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-skills Repository topic
- codex Repository topic
- codex-skill Repository topic
- hermes-agent Repository topic
- openclaw Repository topic
- engineering Derived category
- operations Derived category
- writing Derived category
- security Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Code standards — the change workflow
You are making a code change. This skill is the execution order; it is
stack-agnostic. Adapt every command to the project's actual toolchain: read the
project's own docs (README, CONTRIBUTING, `AGENTS.md`/`CLAUDE.md`, a Makefile or
package scripts) once to learn its build, test, lint, and format commands before
you start.
## Steps
1. **Orient.** Read any project lessons/gotchas file (e.g. `tasks/lessons.md`) and obey it.
Find and read the one doc for the subsystem you're changing, not the whole tree.
2. **Plan if non-trivial** (3+ steps or an architectural choice): short plan in `tasks/todo.md` —
files touched, tests to add, risks. Going sideways → stop and re-plan.