agentleFS
rayketcham-labrayketcham-lab/qn-claude-web/.claude/skills/retro/SKILL.md

retro

Skill2 starsChanged 8 months agoApache-2.0View on GitHub

Post-task retrospective — capture lessons learned and store them for future sessions. Builds cumulative intelligence across sessions.

194 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • ShreyRaviSkill

    plan-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-811Skill

    ios-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

  • seek888Skill

    pair-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

  • timurgaleevSkill

    document-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

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 8

    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
  1. Distinctive:

    After completing a task, capture what went well, what went wrong, and what to do differently.

    line 12
  2. Distinctive:

    Look at the work just completed:

    line 22
  3. Distinctive:

    Read MEMORY.md for task context and decisions made.

    line 27
  4. Distinctive:

    After completing any significant task

    line 77
  5. Distinctive:

    After a debugging session that took longer than expected

    line 78
  6. Distinctive:

    After discovering a non-obvious codebase behavior

    line 79
  7. Distinctive:

    Before ending a session — capture while context is fresh

    line 80
  8. Distinctive:

    When the user says "remember this" or "don't make this mistake again"

    line 81

“Common” is measured: kept by at least 6 in 10 of the 170 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/retro — Retrospective & Lessons Capture

After completing a task, capture what went well, what went wrong, and what to do differently. Store findings in context-store for cumulative intelligence.

Target

$ARGUMENTS

Process

Step 1 — Review What Happened

Look at the work just completed:

git log --oneline -20
git diff --stat main..HEAD

Read MEMORY.md for task context and decisions made.

Step 2 — Identify Lessons

For each of these categories, note anything worth remembering:

What went well (reinforce):

  • Approaches that worked on first try
  • Tools/commands that saved time
  • Patterns that should become standard

What went wrong (prevent):

  • Bugs introduced and their root cause
  • Time wasted on wrong approaches
  • Assumptions that turned out to be false

What was learned (remember):

  • Codebase quirks discovered
  • Configuration gotchas
  • API behaviors that weren't obvious

Step 3 — Store in Context Store

For each lesson worth preserving, call mcp__context-store__store_context with:

  • project: the project name
  • category: lesson
  • title: short, searchable title
  • content: the lesson with context
  • tags: relevant tags for future search

For architectural decisions, also call mcp__context-store__record_decision.

Step 4 — Report

## Retro: [Task]

### Lessons Stored
1. [lesson title] — [one-line summary]
2. [lesson title] — [one-line summary]

### Decisions Recorded
1. [decision] — [rationale in brief]

### Patterns to Watch
- [anything that might recur]

When to Use

  • After completing any significant task
  • After a debugging session that took longer than expected
  • After discovering a non-obvious codebase behavior
  • Before ending a session — capture while context is fresh
  • When the user says "remember this" or "don't make this mistake again"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.