Sup coding
Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish)From its SKILL.md
npx -y skills add chinkan/RustFox --skill sup-codingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 120 tokens by cl100k_base, as published. Nobody here has run it
When to use
When a task is classified as code_change, bug_fix, or refactor.
Operating rules
- Always run inside an isolated branch/worktree.
- Always run formatter, linter, and tests before declaring success.
- Verification evidence: at minimum one passing test or one confirmed diff.
- Prefer test-driven development: write a failing test, then make it pass.
- Keep commits small and logically scoped.
Stop conditions
- All planned changes implemented.
- Verification passes (build, tests, lint, format).
- Reviewer notes are addressed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.