ghe

Configure GitHub Elements plugin for this project

Spawn a background Claude agent in a new Terminal window (macOS only)

Use this agent when CI failures are detected or when automated issue creation is needed. Creates GitHub issues from CI/CD failures. Parses failure logs, extracts relevant details, and creates properly labeled issues linked to the appropriate epic. Examples: <example>Context: CI workflow failed. user: "Create an issue for the CI failure" assistant: "I'll use ci-issue-opener to create a properly formatted issue"</example>

Use this agent when creating DEV threads, resuming DEV work, posting DEV checkpoints, or transitioning DEV to TEST. Manages DEV thread lifecycle for code-heavy development work. Handles thread creation, claiming, checkpointing, and transition to TEST. Examples: <example>Context: Starting new development work. user: "Create a new DEV thread for the authentication feature" assistant: "I'll use dev-thread-manager to create and initialize the DEV thread"</example> <example>Context: DEV work complete, ready for testing. user: "DEV is done, transition to TEST" assistant: "I'll use dev-thread-manager to close DEV and prepare for TEST"</example>

Use this agent when checking for workflow violations during maintenance cycles, when violations are suspected, or for periodic audits. Detects and reports workflow violations in GitHub Elements. Scans for phase order violations, scope violations, and missing checkpoints. Uses progressive enforcement (warn first, block on repeat). Examples: <example>Context: Maintenance cycle. user: "Check for workflow violations" assistant: "I'll use enforcement agent to scan for violations"</example>

Use this agent when managing issues, coordinating threads, running maintenance cycles, or enforcing workflow rules in GitHub Elements. Central orchestrator that manages DEV/TEST/REVIEW thread lifecycle, spawns specialized agents for maintenance, and reports issues to main Claude. Trigger when user mentions "orchestrate", "maintain github elements", "run maintenance cycle", "coordinate threads", "enforce rules". Examples: <example>Context: User wants to start maintenance cycle. user: "Run a maintenance cycle on the github elements" assistant: "I'll use the github-elements-orchestrator to coordinate maintenance across all active threads"</example>

Use this agent when memory needs syncing after checkpoints, thread claims, or thread closures. Synchronizes GitHub Elements with SERENA memory bank. Updates activeContext.md, progress.md, techContext.md based on thread lifecycle events. Examples: <example>Context: Thread just closed. user: "Sync the memory bank after closing DEV" assistant: "I'll use memory-sync to update SERENA"</example>

This skill should be used when updating the project CHANGELOG, tracking requirement changes, recording design decisions, or documenting version history. Uses git-diff to detect and categorize changes to both code and requirements. Trigger on "changelog", "version history", "what changed", or after significant commits.

POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread. USE THIS SKILL WHEN: - User says "post a checkpoint" or "save my progress" - User says "update the issue" or "record current state" - User says "checkpoint" or "save checkpoint" - User completed a milestone and wants to record it - User encountered a blocker and wants to document it - User is about to take a break and wants to save state - Meaningful state change occurred during work PRECONDITION: User must already have an active (claimed, in-progress) thread. DO NOT USE THIS SKILL WHEN: - User wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to FINISH current phase and MOVE to next (use ghe-transition) - User wants reports (use ghe-report) - No active thread exists (must claim first) EXAMPLES: <example> Context: User working on DEV wants to save progress user: "Post a checkpoint" assistant: "I'll use ghe-checkpoint to post your current progress to the active thread" </example> <example> Context: User completed a milestone user: "Save my progress, I finished the authentication module" assistant: "I'll use ghe-checkpoint to record this milestone" </example> <example> Context: User taking a break user: "I need to stop for now, save my work" assistant: "I'll use ghe-checkpoint to save your current state before you go" </example>

CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE THIS SKILL WHEN: - User says "claim issue #N" or "claim #N" - User says "start working on issue #N" or "take issue #N" - User says "I'll work on #N" or "pick up #N" - User wants to BEGIN work on a specific issue number - User selected an issue from available work and wants to claim it REQUIRED: An issue number must be specified or identifiable from context. DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User is ALREADY working and wants to post update (use ghe-checkpoint) - User wants to CHANGE phases (use ghe-transition) - User wants reports (use ghe-report) - No specific issue number is mentioned EXAMPLES: <example> Context: User wants to start work on a specific issue user: "Claim issue #201" assistant: "I'll use ghe-claim to claim issue #201 with the full protocol" </example> <example> Context: User picks from available work user: "I'll take issue #205" assistant: "I'll use ghe-claim to claim issue #205" </example> <example> Context: User wants to start on specific feature user: "Start working on #312" assistant: "I'll use ghe-claim to claim and set up issue #312" </example>

Reference material for Athena when writing requirements. NOT a template - Athena writes requirements freely based on the domain. This skill provides guidance patterns that may be useful, not constraints to follow.

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>

5 hooks across 5 events