Coding Quality Loop
Use when a coding agent must turn a software goal, bug, issue, or refactor into a small, verified, independently reviewed code change.
Install
npx skills add zaingz/coding-quality-loop --skill coding-quality-loopgit clone --depth 1 https://github.com/zaingz/coding-quality-loop.git /tmp/coding-quality-loop
mkdir -p ~/.claude/skills
cp -r /tmp/coding-quality-loop/. ~/.claude/skills/coding-quality-loopPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Coding Quality Loop Goal: the smallest correct change, with evidence a human can trust, review, revert, or merge. This file is the only always-loaded text. Load `references/` only when needed. Workers never load either. ## Orchestrator Layer The main session is the **orchestrator**. It thinks hard and makes every decision; workers only execute. - Orchestrator owns: task class, context map, contract, right-size rung, plan, model routing, verdict on findings, stop-if-unsafe. - Workers (implementer, reviewer) receive a **brief, not context**: goal, contract slice, files, commands, done-check. One screen max. No skill text, no references, no repository tour. - Delegate only to frontier models on Claude Code or Codex (see Routing). Droid is a supported install target outside the routed kernel; delegation to Droid is allowed only when an explicit harness routes it. The reviewer must be fresh context and cannot be the implementer. An implementer worker may persist across fix rounds of one slice (follow-ups return to its cached session; one ledger row per round, same session id); reviewers never persist. Different-family review is the portable default; an explicit higher-level harness may pin the same model across separate hosts/sessions when deterministic gates and supervisor verification retain final truth. ## Task Class (pick the smallest safe) - **tiny** — typo, one-liner. Edit, run the smallest check. No artifacts.
Details
- Skill name
coding-quality-loop- Repository
- zaingz/coding-quality-loop
- License
- MIT
- Repo updated
- 23 October 2026
FAQ
What does the Coding Quality Loop skill do?
Use when a coding agent must turn a software goal, bug, issue, or refactor into a small, verified, independently reviewed code change.
How do I install the Coding Quality Loop skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add zaingz/coding-quality-loop --skill coding-quality-loop. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Coding Quality Loop popular?
It lives in zaingz/coding-quality-loop, which has 6 GitHub stars and 0 forks.
Related skills
Contributor Codebase Analyzer
6anivar/contributor-codebase-analyzer
Deep-dive code analysis with periodic saving. Contributor mode reads every commit diff for annual reviews, accuracy rates, and promotion readiness. Codebase mode maps repository structure, cross-repo relationships, and enterprise governance. Works with GitHub (gh) and GitLab (glab). Saves checkpoints incrementally for resume across sessions.
Codesplain
6opitaru-sys/codesplain
Use when working in a coding project owned by a non-coder - when the project root contains CODESPLAIN.md, when the user invokes /codesplain (to bootstrap a project or ask a question), when a consequential technical decision comes up during building, or when explaining a bug or fix to the owner in plain language.
Icode
5ayukyo/icode-skill
ICODE 端到端编码工作流，适配 Claude Code、Codex、CodeBuddy、WorkBuddy。用户调用 /icode、$icode，或说“使用 ICODE”“用 icode 帮我”“让 ICODE”“Use ICODE”完成开发、日志分析、设计/代码审查、证据验证、独立复评、文档/Word/PPT、学习、工单管理等任务时使用；也用于已绑定 ICODE 工单的续接。Use when users explicitly request ICODE for an AI coding workflow, ticket-based development, code review, log analysis, documentation, or evidence verification; also use to resume a bound ICODE ticket. 支持自然语言目标与限制，不要求背命令；能力咨询只解释不执行。保留全部 /icode 子命令，复用既有步骤与安全门禁，不接管未指定 ICODE 的普通请求。
Code Forge
6tercel/code-forge
Complete Codex development workflow for turning requirements, feature docs, or prompts into working code. Use when the user asks to plan implementation work, execute tasks, enforce TDD, review source code, fix bugs, debug failures, verify completion, manage worktrees or branch finishing, dispatch parallel agents, port a project to another language, check progress, or run an end-to-end build flow. Supports complex orchestration across plan -> impl -> review -> fix -> verify, plus build, forge smart dispatch, worktree, finish, parallel, port, tdd, debug, and status workflows. Every workflow here
Khaow Friend Roleplay
513D4C/kewmajiroon8888
Roleplay as a friend named "khaow" — a quirky programmer who solves problems in weird, roundabout ways but is extremely confident in his own ideas. Use this skill whenever the user mentions their friend khaow, asks to roleplay as khaow, wants to talk to khaow, or asks "how would khaow do this?" / "what would khaow build?" — even if the word "roleplay" isn't used directly.
Code Animations
5beriki770-ship-it/code-animations
Make "code-rendered" animated videos where a program draws every frame (Canvas 2D + procedural Web Audio), rendered headless to MP4 in 16:9 / 9:16 / 4:5 from one timeline. Use for animated explainers, technical walkthroughs, diagrams in motion, and procedural sound or music, where the output should be editable code and not generated pixels.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.