ghe-report
Generate detailed workflow reports with metrics, health assessments, and epic-specific analysis for GitHub Elements. Covers throughput, cycle times, compliance status, and thread history.
Best use case
ghe-report is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate detailed workflow reports with metrics, health assessments, and epic-specific analysis for GitHub Elements. Covers throughput, cycle times, compliance status, and thread history.
Teams using ghe-report should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ghe-report/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ghe-report Compares
| Feature / Agent | ghe-report | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate detailed workflow reports with metrics, health assessments, and epic-specific analysis for GitHub Elements. Covers throughput, cycle times, compliance status, and thread history.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## IRON LAW: User Specifications Are Sacred **THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.** 1. **Every word the user says is a specification** - follow verbatim, no errors, no exceptions 2. **Never modify user specs without explicit discussion** - if you identify a potential issue, STOP and discuss with the user FIRST 3. **Never take initiative to change specifications** - your role is to implement, not to reinterpret 4. **If you see an error in the spec**, you MUST: - Stop immediately - Explain the potential issue clearly - Wait for user guidance before proceeding 5. **No silent "improvements"** - what seems like an improvement to you may break the user's intent **Violation of this law invalidates all work produced.** ## Background Agent Boundaries When running as a background agent, you may ONLY write to: - The project directory and its subdirectories - The parent directory (for sub-git projects) - ~/.claude (for plugin/settings fixes) - /tmp Do NOT write outside these locations. --- ## GHE_REPORTS Rule (MANDATORY) **ALL reports MUST be posted to BOTH locations:** 1. **GitHub Issue Thread** - Full report text (NOT just a link!) 2. **GHE_REPORTS/** - Same full report text (FLAT structure, no subfolders!) **Report naming:** `<TIMESTAMP>_<title or description>_(<AGENT>).md` **Timestamp format:** `YYYYMMDDHHMMSSTimezone` **Example:** `20251206200000GMT+01_status_report_(Hermes).md` **ALL 11 agents write here:** Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus **REQUIREMENTS/** is SEPARATE - permanent design documents, never deleted. **Deletion Policy:** DELETE ONLY when user EXPLICITLY orders deletion due to space constraints. DO NOT delete during normal cleanup. --- ## Settings Awareness Respects `.claude/ghe.local.md`: - `enabled`: If false, return minimal report - `notification_level`: verbose/normal/quiet - affects detail level - `stale_threshold_hours`: Used for stale thread detection --- # GitHub Elements Report (Detailed Analysis) **Purpose**: Generate detailed reports with metrics, health assessment, or epic analysis. More comprehensive than quick status. ## Report Types ### 1. Metrics Report Performance indicators and trends: - Throughput (features completed, bugs fixed) - Cycle times (average sessions per phase) - First-pass REVIEW rate - Demotion rate - Agent performance comparison ### 2. Health Report Workflow compliance assessment: - Rule compliance status - Stale threads detection - Violation history - Memory bank synchronization status - Overall health score ### 3. Epic Report Single epic deep dive: - Thread history (all DEV/TEST/REVIEW cycles) - Current phase and progress - Key technical decisions - Remaining work estimation ## When to Use - Performance analysis - Compliance audits - Epic-specific status - Trend analysis - Health assessment ## How to Execute Spawn **reporter** agent with appropriate report type: ``` reporter(type="metrics") → Performance report reporter(type="health") → Compliance report reporter(type="epic", epic="epic-name") → Epic report ``` ## Output Formats ### Metrics Report ```markdown ## GitHub Elements Metrics Report ### Throughput | Metric | Value | Trend | |--------|-------|-------| | Features completed | N | +/- vs last week | | Bugs fixed | N | +/- vs last week | ### Cycle Times | Phase | Avg Duration | Issues Processed | |-------|--------------|------------------| | DEV | N sessions | N | | TEST | N sessions | N | | REVIEW | N sessions | N | ### Quality Metrics - First-pass REVIEW rate: N% - Demotion rate: N% - Test coverage (avg): N% ``` ### Health Report ```markdown ## GitHub Elements Health Report ### Compliance Status | Rule | Status | Notes | |------|--------|-------| | One thread at a time | PASS/FAIL | | | Phase order | PASS/FAIL | | | Checkpoint frequency | PASS/WARN | | ### Stale Threads [Threads with no activity > 24h] ### Violation History [Recent violations and resolutions] ### Overall Health [HEALTHY / WARNINGS / CRITICAL] ``` ### Epic Report ```markdown ## Epic Report: [Epic Name] ### Thread History | Issue | Type | Status | Duration | |-------|------|--------|----------| ### Current Phase [Current phase with progress] ### Key Decisions [Technical decisions made] ### Remaining Work [Estimated remaining effort] ``` ## Key Differentiator This skill provides DETAILED ANALYSIS. For a quick current-state overview, use `ghe-status` instead.
Related Skills
recipe-generate-report-from-sheet
Read data from a Google Sheet and create a formatted Google Docs report.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
gws-admin-reports
Google Workspace Admin SDK: Audit logs and usage reports.
power-bi-report-design-consultation
Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.
creating-oracle-to-postgres-migration-bug-report
Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.
../../../engineering-team/playwright-pro/skills/report/SKILL.md
No description provided.
daily-news-report
Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.
lark-workflow-standup-report
日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。
reporting-sprints
Use this skill when you need to report on a sprint
reporting-issues
Use this skill when you need to report on a troubleshooting session
report-writing
작업 완료 후 상세 리포트 문서를 작성. 변경 이력, 영향도 분석, 검증 결과를 문서화할 때 사용. 파일명 규칙 YYYY-MM-DD-<제목>-report.md
infrastructure-reporting
Generate comprehensive network infrastructure reports including health status, performance analysis, security audits, and capacity planning recommendations.