Agent skill

epic-report

Generate epic progress reports. Use for epic status, story tracking, blocker detection, and progress summaries.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill epic-report --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/analysis/epic-report/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /epic-report - Epic Completion Report Generate a completion report for an epic. ## Usage ``` /epic-report <epic-number> ``` **Example:** ``` /epic-report 441 ``` ## What This Skill Does 1. **Fetches Epic Data** - Uses `gh issue view` to get epic details 2. **Finds Related Issues** - Searches for issues mentioning the epic 3. **Analyzes Completion** - Checks status of each story/task 4. **Detects Blockers** - Finds TODOs in changed files 5. **Generates Report** - Creates structured markdown ## Report Sections ### 1. Epic Summary - Title and objective - Overall completion percentage - Date range ### 2. Stories Status Table | Story | Title | Status | Notes | |-------|-------|--------|-------| | #442 | Story title | Complete | | | #443 | Story title | In Progress | Blocked by X | ### 3. Test Results Summary - Total tests run - Passed/Failed/Skipped - Link to Allure report if available ### 4. Artifacts Created - New files added - Modified files - Location and purpose ### 5. Blocking Issues - TODOs found in code - Failing tests - Open dependencies ### 6. Next Steps - Recommended follow-up actions - Issues to create - Documentation needed ## Implementation Notes To generate the report,

What's inside
Steps it walks through
  1. Usage
  2. What This Skill Does
  3. Report Sections
  4. 1. Epic Summary
  5. 2. Stories Status Table
  6. 3. Test Results Summary
  7. 4. Artifacts Created
  8. 5. Blocking Issues
  9. 6. Next Steps
  10. Implementation Notes
  11. Output Format
Ships with 1 file
  • metadata.json
Commands it runs
gh issue view <epic-number> --repo krazyuniks/guitar-tone-shootout --json title,body,state
gh issue list --repo krazyuniks/guitar-tone-shootout --search "epic:<epic-number>" --json number,title,state
git diff main...HEAD --name-only | xargs grep -n "TODO:" 2>/dev/null || true
ls -la tests/allure-report/index.html 2>/dev/null
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the epic-report skill do?

Generate epic progress reports. Use for epic status, story tracking, blocker detection, and progress summaries.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill epic-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.