Individual skill
sup-coding
Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish)
skills/sup-coding/SKILL.md
Source commit 17f18581edf64d65b296f5ad10c20170025f09b3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 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)
- 11
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agent Repository topic
- embeddings Repository topic
- llm Repository topic
- mcp Repository topic
- openclaw Repository topic
- openrouter Repository topic
- openrouter-api Repository topic
- rust Repository topic
- engineering Derived category
- design Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 787 bytes
Read excerpt
## When to use
When a task is classified as code_change, bug_fix, or refactor.
## Operating rules
1. Always run inside an isolated branch/worktree.
2. Always run formatter, linter, and tests before declaring success.
3. Verification evidence: at minimum one passing test or one confirmed diff.
4. Prefer test-driven development: write a failing test, then make it pass.
5. Keep commits small and logically scoped.
## Stop conditions
- All planned changes implemented.
- Verification passes (build, tests, lint, format).
- Reviewer notes are addressed.