ghe-report
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>
What this skill does
## 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 in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.