self-improvement-loop

Automates cross-cutting project reviews, improvement issue triage, and backlog refinement on GitHub.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill self-improvement-loop-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-improvement-loop
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/self-improvement-loop
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill self-improvement-loop-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Improvement work in a project tends to pile up: issues get filed but never prioritized, low-priority items starve forever, and no one steps back to find the root cause behind recurring symptoms. This Skill runs a self-improvement loop that periodically reviews the whole project, files root-cause improvement issues, grooms the backlog, and implements the top item autonomously. ## Core Features & Use Cases - Discovery mode: Launches parallel review agents across N project-defined perspectives (pipeline health, repository hygiene, artifact quality, codebase, strategy) to identify meta root causes and file deduplicated improvement issues with priority and story-point labels. - Grooming mode: Aggregates open improvement issues via a triage script, closes clear duplicates and stale items, creates Epic tracking issues, and runs a weekly refinement gate that forces every stagnant issue into one of four exits (work on it, drop it, bundle it, defer it) with circuit breakers against infinite deferral. - Consumption mode: Daily digestion of up to 5 ready issues sorted by priority with tie-breaking rules, hold circuit breakers, and automatic retrospective handoff after merges. - Use Case: A team maintaining an active GitHub repository schedules this Skill so that every week stagnant issues are refined, every day the top improvement is implemented and merged via PR, and every month the backlog is groomed into Epics. ## Quick Start Ask the AI to run a cross-cutting review of the project and file improvement issues for the root causes it finds.

Frequently Asked Questions about self-improvement-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a project-wide code and process review?▼

Run the discovery mode, which launches parallel review agents across project-defined perspectives such as pipeline health, repository hygiene, and codebase quality. Each agent returns strengths, critical issues with evidence, and a score, which are merged into root-cause analysis.

How to groom a large backlog of GitHub improvement issues?▼

Use the grooming mode: it runs triage_improvements.py to aggregate issues by priority, category, and duplication, then closes clear duplicates, creates Epic tracking issues for clustered categories, and fills missing priority and story-point labels through the product owner agent.

Can this Skill work without the gh CLI installed?▼

Yes. In cloud environments where gh is unavailable, all GitHub operations are routed through the mcp__github__* MCP tools instead, following the fallback mapping documented in the project rules. Local runs can use gh directly.

What prevents stagnant issues from being deferred forever?▼

The refinement gate forces every targeted issue into one of four exits: work on it, drop it, bundle it into an Epic, or defer with a concrete re-entry condition. Circuit breakers block a third consecutive deferral and force escalation after repeated holds.

Does the Skill close issues automatically without user confirmation?▼

It autonomously closes only clear duplicates and stale issues verified against the code, always leaving a reopen path in the comment. Ambiguous cases are kept open with cross-linking comments, and milestone creation still requires user confirmation.

When should I not use the consumption mode?▼

Avoid it for issues owned by other lanes: retro-try items belong to the retrospective lane, and SP-n sprint issues belong to the sprint development lane. The mode also defers large or ambiguous issues after recording a design comment.