coding-quality-loop
SolidUse when a coding agent must turn a software goal, bug, issue, or refactor into a small, verified, independently reviewed code change.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- zaingz
- Repository
- zaingz/coding-quality-loop
- Created
- 1 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
code-standards
Apply Parler Protocol's engineering contract to a code change. Use whenever implementing a feature, fixing a bug, or refactoring in this repo — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces the hard gates (never cargo fmt, clippy -D warnings, make ci green, additive wire changes only, security invariants).
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).
loop-review
Independently review one loop iteration's implementation diff against the product contract and report a verdict (APPROVE, REVISE with must-fix items, or — at the gate — ESCALATE to the human). Requirement-first — per-REQ satisfaction is judged before code quality; the gate renders a machine-parsed verdict per REQ. Runs read-only with fresh context; driven by loop.sh, not for ad-hoc use.