OpenParable
Skip to content
← Back to skills

Epic Report

Productivity
epic-report

Epic Report is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/analysis/epic-report/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/epic-report, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

/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

StoryTitleStatusNotes
#442Story titleComplete
#443Story titleIn ProgressBlocked 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, execute these steps:

  1. Get Epic Details:

    gh issue view <epic-number> --repo krazyuniks/guitar-tone-shootout --json title,body,state
    
  2. Find Related Issues:

    gh issue list --repo krazyuniks/guitar-tone-shootout --search "epic:<epic-number>" --json number,title,state
    
  3. Check for TODOs in Changed Files:

    git diff main...HEAD --name-only | xargs grep -n "TODO:" 2>/dev/null || true
    
  4. Check for Allure Reports:

    ls -la tests/allure-report/index.html 2>/dev/null
    

Output Format

Generate the report as markdown and output it directly to the conversation. The report should be structured, scannable, and include links to relevant issues.