Generates KPT retrospectives and records qualified Try items as GitHub Issues.
npx skills add https://github.com/kai-kou/gem-hunter --skill retrospective-kai-kou
Please help me install this Agent Skill. Skill: retrospective Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/retrospective Command: npx skills add https://github.com/kai-kou/gem-hunter --skill retrospective-kai-kou
type:retro-try Issues when eligibility criteria are met, preventing tracker noise. - Failure-triggered Retros: Automatically runs on circuit-breaker activation, repeated errors, or quality gate failures so root-cause prevention measures accumulate without manual requests. - Use Case: After a content-generation pipeline finishes (or fails twice with the same error), invoke the retrospective to get a KPT summary, Slack notification, ledger updates, and deduplicated improvement Issues with priority escalation on recurrence. ## Quick Start Ask the AI to run a retrospective on the latest pipeline execution, for example by saying "レトロスペクティブして" or "/retrospective {pipeline} {ID}".High-intent search queries and answers about installing and using this skill.
Invoke the skill manually with "/retrospective {pipeline} {ID}" or phrases like "レトロスペクティブして". Pipelines also call it automatically as their final step, passing pipeline name, entity ID, PR URL, and execution summary.
Try items are promoted only if they are urgency:blocker, or observed at least twice within the observation window while open non-blocker issues are under the WIP limit. All other Try items are recorded in a candidate ledger Issue instead of creating new Issues.
Yes. It auto-triggers on circuit-breaker activation, the same error occurring twice or more, quality gate misses, and unresolved self-review errors. One-off minor errors resolved by retry can be skipped.
No. In cloud environments the gh CLI is blocked by an egress proxy, so all GitHub operations must go through GitHub MCP tools (mcp__github__*). The gh command examples in the skill are local-environment alternatives only.
The skill adds a recurrence comment to the existing Issue instead of creating a duplicate, and escalates its priority label to priority:high after more than three recurrences. Closed not_planned Issues are reopened on recurrence.
The ledger relies on exact key matching, so semantically identical issues phrased differently may be undercounted. Concurrent sessions can lose at most one observation between read and write, which is recovered from the audit-log comments on the next run.
NVIDIAValidate EAGLE3 pipeline runs by checking completion, artifacts, and benchmark metrics.
ClementWalterAutomate Git commit hygiene, PR readiness, and issue linking workflows.
MykhailoDmytriakhaCapture durable lessons from solved problems and update MEMORY.md.
calebeynonTranscribe handwritten images into standalone LaTeX fragments as .tex files.