channingwalton

6 mods across 1 repository, 2 stars between them.

chatter

01

channingwalton/skills

Skill Claude CodeCodex

Use when the user asks you to start, join, or continue a conversation with other agents via chatter, agent-chat, or talking to other agents about X.

2 16d ago A 35 tokens original MIT

code-reviewer

02

channingwalton/skills

Skill Claude CodeCodex

Read-only code review agent. Use when the user explicitly asks for a review, or when invoked by the fix-loop skill, to find correctness, security, performance, maintainability, and missing-test risks. Does not auto-trigger after routine code changes — software-development owns implementation review through fix-loop.

2 16d ago A 63 tokens original MIT

fix-loop

03

channingwalton/skills

Skill Claude CodeCodex

Iterative review-fix cycle that runs code-reviewer then repairs Critical issues until none remain. Use when the user says "review and fix", "find and fix bugs", "clean up the code", "fix all issues", "review then fix", or otherwise asks to both find and repair problems.

2 16d ago A 64 tokens original MIT

requirements-report

04

channingwalton/skills

Skill Claude CodeCodex

Link Markdown requirements to tests and render pass, fail, or untested traceability from JUnit XML. Use before writing tests whenever requirements or a specification drive implementation, and for living requirements, acceptance criteria tied to tests, finding untested requirements, or mapping a failure to its…

2 16d ago A 78 tokens original MIT

retrospective

05

channingwalton/skills

Skill Claude CodeCodex

Use on a fortnightly or post-milestone cadence, or when the user says "retrospective" / "retro" / "what's been recurring" / "what did we learn" / "review the last few sessions". Reads multiple session transcripts, distils each, measures token-weighted wasted effort (including abandoned-and-restarted sessions), and…

2 16d ago A 116 tokens original MIT

channingwalton/skills

Skill Claude CodeCodex

Software development workflow for implementation work that changes code or tests. Use when asked to implement, modify, or fix software behaviour; do not use for shell help, Git-only work, read-only investigation, configuration questions, or general explanation unless code changes are requested. Coordinates planning…

2 16d ago A 67 tokens original MIT