ghe-report

Description

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>

Tool Access

Full access

Inherits all available tools

Supporting Files

0 files

Additional assets for this skill

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Links

GitHub Stats

0 forks

Updated 10 days ago

Related Skills

Agent Development

45.7K

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

45.7K

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev

Hook Development

45.7K

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

From plugin-dev