superpowers
Skill1 starsChanged 47 days agoMITView on GitHub
Use a dependable planning, execution, review, and verification workflow for multi-step engineering tasks.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
- ZhouYinLong-lab/Dog-Skillstheir own version, first seen Nov 8, 2026
- salmandev/everything-geminitheir own version, first seen Nov 1, 2026
- lucasnscr/issue-to-pr-aitheir own version, first seen Oct 25, 2026
- Peiiii/nextclawtheir own version, first seen Oct 8, 2026
- belos-street/skill-kittheir own version, first seen Sep 16, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- Peiiii/nextclaw★ 263same name
- alebgl77/claude-inc★ 21same name
- belos-street/skill-kit★ 8same name
- ZhouYinLong-lab/Dog-Skills★ 7same name
- HK-hub/AgentSkills★ 6same name
- Agnik47/claude-skills★ 3same name
- grasscaograss/AwesomeWeldoneSkills★ 2same name
- hillwang1983-web/agent-factory★ 2same name
- salmandev/everything-gemini★ 2same name
- kazemcodes/skill-tree★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- build-web-appsSkill
- cavemanSkill
- composioSkill
- context7Skill
- diagnoseSkill
- frontend-testing-debuggingSkill
- gitnexusSkill
- grill-meSkill
- security-auditSkill
- tddSkill
- to-prdSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this workflow for multi-step code changes, integrations, and substantial debugging.
- Very specific: line 17
Use read_skill for a relevant specialist workflow such as tdd, diagnose, security-audit, build-web-apps, or gitnexus.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Engineering workflow
Use this workflow for multi-step code changes, integrations, and substantial debugging. Keep small, obvious edits lightweight.
- Understand: Inspect the workspace, active instructions, relevant files, and current Git changes. Separate facts from assumptions. Ask only for information that blocks a safe, correct result.
- Plan: Break multi-step work into observable outcomes with
todo_write. Keep the plan proportional to the task. If the user explicitly asks to approve a plan first, stop at that boundary. - Execute: Make the smallest coherent changes that meet the request. Follow existing architecture, reuse existing tools, and update task progress as work advances.
- Review: Inspect the resulting diff and affected call paths. Look for regressions, security issues, stale docs, and changes outside the requested scope.
- Verify: Gather direct evidence for the requested outcome. Run automated tests only when the user asks for tests or verification. State exactly what was and was not checked; never infer success from an action being started.
Use read_skill for a relevant specialist workflow such as tdd, diagnose, security-audit, build-web-apps, or gitnexus. These workflows do not replace Kratos's permission checks or the user's instructions. Keep reasoning on the configured Kratos model.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.