Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ghe
Generate DETAILED reports with metrics, health checks, or epic-specific analysis. More comprehensive than quick status overview. USE THIS SKILL WHEN: - User asks for "metrics" or "statistics" or "performance report" - User asks for "health check" or "workflow health" or "compliance check" - User asks for "epic report" or "epic status for X" - User asks for "detailed report" or "comprehensive report" - User asks "how are we performing" or "what's our throughput" - User asks about "cycle times" or "demotion rates" - User wants analysis, not just current state REPORT TYPES: - metrics: Throughput, cycle times, first-pass rates, demotion rates - health: Compliance status, stale threads, violation history, memory bank status - epic: Single epic details with thread history, progress, decisions DO NOT USE THIS SKILL WHEN: - User just wants QUICK status overview (use ghe-status) - User wants to CLAIM an issue (use ghe-claim) - User wants to POST a checkpoint (use ghe-checkpoint) - User wants to TRANSITION phases (use ghe-transition) KEY DIFFERENCE FROM ghe-status: - ghe-status = quick overview, current state, what's active - ghe-report = detailed analysis, metrics, trends, health assessment EXAMPLES: <example> Context: User wants performance metrics user: "Show me the workflow metrics" assistant: "I'll use ghe-report with type 'metrics' for detailed performance analysis" </example> <example> Context: User wants to check workflow compliance user: "Run a health check on the workflow" assistant: "I'll use ghe-report with type 'health' to assess workflow compliance" </example> <example> Context: User wants details on specific epic user: "Give me a report on the jwt-auth epic" assistant: "I'll use ghe-report with type 'epic' for jwt-auth" </example> <example> Context: User asks about performance trends user: "What's our first-pass review rate?" assistant: "I'll use ghe-report with type 'metrics' to get performance statistics" </example>
npx claudepluginhub Emasoft/ghe-marketplace --plugin gheHow this skill is triggered — by the user, by Claude, or both
Slash command
/ghe:skills/ghe-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.**
Generates pipeline analytics reports from issue tracker and git data — success rate, per-agent effectiveness, failure patterns, optional HTML dashboard.
Displays a work status dashboard for AgentOps workflow, showing current tasks, recent activity, git state, and inbox. Use /status to get a single-screen overview.
Analyzes git commit history for engineering retrospectives, tracking work patterns, code quality metrics, trends, per-person breakdowns, shipping streaks, and actionable improvements. Use for 'retro', weekly reviews, or 'what did we ship'.
Share bugs, ideas, or general feedback.
THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.
Violation of this law invalidates all work produced.
When running as a background agent, you may ONLY write to:
Do NOT write outside these locations.
ALL reports MUST be posted to BOTH locations:
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.
Respects .claude/ghe.local.md:
enabled: If false, return minimal reportnotification_level: verbose/normal/quiet - affects detail levelstale_threshold_hours: Used for stale thread detectionPurpose: Generate detailed reports with metrics, health assessment, or epic analysis. More comprehensive than quick status.
Performance indicators and trends:
Workflow compliance assessment:
Single epic deep dive:
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
## 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%
## 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: [Epic Name]
### Thread History
| Issue | Type | Status | Duration |
|-------|------|--------|----------|
### Current Phase
[Current phase with progress]
### Key Decisions
[Technical decisions made]
### Remaining Work
[Estimated remaining effort]
This skill provides DETAILED ANALYSIS. For a quick current-state overview, use ghe-status instead.