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.
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 General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.