> common-session-retrospective
Analyze conversation corrections to detect skill gaps and auto-improve the skills library. Use after any session with user corrections, rework, or retrospective requests. (triggers: **/*.spec.ts, **/*.test.ts, SKILL.md, AGENTS.md, retrospective, self-learning, improve skills, session review, correction, rework)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/common-session-retrospective?format=md"Session Retrospective
Priority: P1 (OPERATIONAL)
Structure
common/session-retrospective/
├── SKILL.md # Protocol (this file)
└── references/
└── methodology.md # Signal tables, taxonomy, report template
Protocol
- Extract — Scan for correction signals (loops, rejections, shape mismatches, lint rework)
- Classify — Root cause: Skill Missing | Incomplete | Example Contradicts Rule | Workflow Gap | Trigger Miss
- Trigger Miss Check — For every task in the session, ask: "Was a relevant skill available but not loaded?"
- If yes: record skill ID, indirect phrase used, and fix (add keyword alias to triggers)
- Propose — One fix per root cause: update skill, update reference, new skill, or new workflow
- Implement — Apply to all agent dirs. Keep SKILL.md concise; move large tables to
references/. UpdateAGENTS.md - Report — Output correction count, skills changed, trigger misses found, estimated rounds saved
Trigger Miss Output
Emit a trigger miss block (schema in references/methodology.md) for each miss detected.
Guidelines
- Cite specifics: Reference concrete conversation moment per proposal
- Extend first: Search
AGENTS.mdbefore creating — update existing skills - One fix per loop: One correction → one targeted skill change
- Sync all agents: Apply to every agent skill dir listed in
.skillsrcagentsfield - Follow skill-creator: New skills comply with
common/skill-creatorstandards
Anti-Patterns
- No Vague Proposals: Cite exact gap + fix, not "make X better"
- No Duplicate Skills: Search AGENTS.md index first
- No Oversized Patches: Extract to
references/per skill-creator standard
References
Signal tables, root cause taxonomy, report template, real-world example: references/methodology.md
> related_skills --same-repo
> common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app. (triggers: generate changelog, app store notes, play store release, what's new, release notes, ve
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)