retro
Skill2 starsChanged 8 months agoMITView on GitHub
Weekly or on-demand retrospective from git history and session logs. Analyzes what got done, work patterns, quality trends, and improvement areas.
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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- examples/CLAUDE.mdCLAUDE.md
- claudeceptionSkill
- closeSkill
- ideaSkill
- investigateSkill
- office-hoursSkill
- plan-ceo-reviewSkill
- reflectSkill
- reviewSkill
- scopeSkill
- shipSkill
- startSkill
- tddSkill
- verify-before-doneSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
3
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 13
Look at what actually happened, not what you remember happening.
- Distinctive: line 19
When you feel busy but aren't sure if you're making progress
- Distinctive: line 20
Before planning the next phase of work
- Very specific: line 92
Write the retro to memory/retro-YYYY-MM-DD.md for future reference.
“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
Retro
The Rule
Look at what actually happened, not what you remember happening.
When to Use
- Weekly review ("what did we accomplish this week?")
- End of a sprint or milestone
- When you feel busy but aren't sure if you're making progress
- Before planning the next phase of work
How It Works
Step 1: Gather the Data
Pull from three sources:
Git history (if available):
- Commits in the time window
- Files changed, lines added/removed
- Patterns (which areas of the codebase got the most attention)
Session logs (from memory/ daily logs):
- Sessions completed
- Major decisions made
- Gotchas encountered
- Skills invoked
Step 2: Categorize the Work
Group everything into:
| Category | What counts |
| Building | New features, new skills, new infrastructure |
| Fixing | Bug fixes, incident response, regression fixes |
| Maintaining | Updates, dependency bumps, config changes, cleanup |
| Planning | Architecture decisions, PRDs, research sessions |
| Learning | New skills created, gotchas documented, process improvements |
Step 3: Identify Patterns
Look for:
- Time sinks — areas that consumed disproportionate effort
- Repeat offenders — the same type of problem appearing multiple times
- Unplanned work — how much of the week was reactive vs. planned
- Momentum — which projects moved forward vs. stalled
Step 4: Produce the Report
## Retro: [Date Range]
### What Got Done
- [Bullet summary of shipped/completed work]
### Time Distribution
| Category | Approximate % |
|----------|--------------|
| Building | XX% |
| Fixing | XX% |
| Maintaining | XX% |
| Planning | XX% |
| Learning | XX% |
### Patterns
- [Observation about work patterns]
- [Recurring issues]
### What Went Well
- [Specific things that worked]
### What Could Improve
- [Specific, actionable improvements]
### Next Week Focus
- [Top 1-3 priorities based on the retro]Step 5: Save
Write the retro to memory/retro-YYYY-MM-DD.md for future reference.
Key Principle
Retros are about patterns, not blame. The goal is to spot systemic issues and adjust — not to judge individual sessions.
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.