retro
Skill1 starsChanged 4 months agoMITView on GitHub
Finds what you had to explain more than once during this work and proposes concrete diffs to CLAUDE.md, skills, or agent roles so the next project starts smarter.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- rodeyseijkens/skillstheir own version, first seen Nov 8, 2026
- Yesterday-AI/ytstacktheir own version, first seen Nov 8, 2026
- gaoyu06/harnesstheir own version, first seen Nov 8, 2026
- Schepetkov/claude-skills-game-UEtheir own version, first seen Nov 8, 2026
- tornikegomareli/Skillstheir own version, first seen Nov 8, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use plan-tune, ios-clean and 10 more.
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.
ShreyRaviSkillplan-tune
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.
Also in 9 projects that use this
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
- Saqlain-811Skill
ios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
seek888Skillpair-agent
Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".
Also in 11 projects that use this
- ShreyRaviSkill
landing-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 8 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
- +1 more from Saqlain-811
- +2 more from ShreyRavi
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- mattpocock/skills★ 309ksame name
- garrytan/gstack★ 141ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- withcoral/coral★ 4.9ksame name
- bergside/awesome-design-skills★ 2.9ksame name
- MiniMax-AI/minimax-code★ 2.2ksame name
- DenchHQ/DenchClaw★ 1.7ksame name
- DenchHQ/ironclaw★ 1.7ksame name
183 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autopilotSkill
- boardSkill
- execute-ticketSkill
- next-ticketSkill
- planSkill
- ponytailSkill
- shipSkill
- specSkill
- unblockSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Prefer skills over CLAUDE.md when there is any doubt: CLAUDE.md costs context in every session, a skill costs nothing until invoked.
- Distinctive: line 49
Cut as well as add: If something in CLAUDE.md or a role went unused or actively misled, propose removing it.
“Common” is measured: kept by at least 6 in 10 of the 171 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
Focus: $ARGUMENTS
The template is meant to be a compounding asset. This command is how it compounds: turn what was learned into configuration, so it is not re-learned next time.
What to look for
Go back over this session and find:
- Repeated corrections. Anything the human had to say more than once — a convention, a preference, a constraint, a "no, not like that". Every repetition is a missing line of configuration.
- Wrong assumptions. Where an agent guessed about the codebase and guessed wrong.
That is usually a gap in
CLAUDE.mdor indocs/QUICK_REF.md. - Friction. Steps that were manual and did not need to be. Permission prompts that fired repeatedly for something obviously safe.
- Role failures. Cases where an agent did something outside its remit, or lacked a tool it genuinely needed.
Where each fix belongs
| Finding | Goes to |
| A project fact, always true, needed every session | CLAUDE.md — but keep it under 200 lines |
| A procedure with steps, needed occasionally | a new skill in .claude/skills/ |
| How one role should behave | that role in .claude/agents/ |
| A safe command prompting every time | permissions.allow in .claude/settings.json |
| A decision and its reasoning | a new ADR in docs/decisions/ |
| A recurring gotcha | docs/QUICK_REF.md, if it stays under 50 lines |
Prefer skills over CLAUDE.md when there is any doubt: CLAUDE.md costs context in every
session, a skill costs nothing until invoked.
Rules
- Propose concrete diffs, not advice. "Be clearer about testing" is useless; the exact
lines to add to
dev.mdare not. - Cite the evidence. For each proposal, name what happened that justifies it. A proposal you cannot ground in something that actually occurred is speculation, and it will cost context forever while helping nobody.
- Cut as well as add. If something in
CLAUDE.mdor a role went unused or actively misled, propose removing it. Configuration that only grows becomes noise. - Be honest about your reach: you see this session. Patterns from other sessions are not visible to you, so do not present a single occurrence as a trend.
Show the proposed diffs and let the human choose. Apply only what they approve, then remind them these changes belong committed back to the template repository, not just to the current project.
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.