Skill Creator
Emasoft
12 published skills · 36 GitHub stars across the catalog. View on GitHub ↗
ghe-changelog
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.
ghe-checkpoint
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 workPRECONDITION: 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 progressuser: "Post a checkpoint"assistant: "I'll use g
ghe-claim
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 itREQUIRED: 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 mentionedEXAMPLES:<example>Context: User wants to start work on a specific issueuser: "Claim issue #201"assistant: "I'll use ghe-claim to claim issue #201 with the full protocol"</example><example>Context: User picks from
ghe-design
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.
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 stateREPORT 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, decisionsDO 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 (u
ghe-requirements
This skill should be used when creating, updating, linking, or versioning requirements for GitHub Elements threads. Use when user mentions requirements, specs, REQ files, or when starting feature development. Provides the requirements folder structure, versioning system, and SERENA backup protocols.
ghe-status
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance.USE THIS SKILL WHEN:- User asks "what's the status" or "show me the status"- User asks "what threads are active" or "what am I working on"- User asks "show me the workflow state" or "what's happening"- User wants a quick overview before starting work- Starting a session and need contextDO NOT USE THIS SKILL WHEN:- 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)- User wants DETAILED metrics/health reports (use ghe-report)EXAMPLES:<example>Context: User starting a session wants to see current stateuser: "What's the github elements status?"assistant: "I'll use ghe-status to show you the current workflow state"</example><example>Context: User wants to know what work is availableuser: "Show me what threads are active"assistant: "I'll use ghe-status to disp
ghe-thread-manager
Use this skill when the user expresses ANY intent related to issue/thread management:- Switching issues: "let's work on X", "switch to #Y", "go to the auth issue"- Checking status: "what are we working on?", "current issue?", "status?"- Background work: "what's in background?", "any features ready?", "check progress"- Starting development: "implement X", "add feature", "fix bug Y", "build a..."- Joining reviews: "let me see the review", "check that feature", "join #X"- Pausing/resuming: "pause this", "come back later", "resume #X"- Stopping transcription: "stop tracking", "don't record this", "private mode"- Resuming last session: "what were we working on?", "resume last issue", "continue where we left off"- Any natural expression of wanting to change focus or check work statusThis skill interprets natural language - users should NOT memorize commands.For the full GHE workflow protocol, see skill: github-elements-tracking
ghe-transition
CHANGE phases in the GitHub Elements workflow. Closes current thread and opens next phase thread. This is a PHASE CHANGE operation, not just saving progress.USE THIS SKILL WHEN:- User says "transition to TEST" or "move to REVIEW"- User says "I'm done with DEV, start TEST" or "DEV complete"- User says "advance to next phase" or "close this phase"- User says "demote to DEV" (from TEST or REVIEW)- User says "tests pass, ready for review"- User says "merge this" (after REVIEW PASS)- User explicitly wants to END current phase and BEGIN nextDO NOT USE THIS SKILL WHEN:- User just wants to SEE status (use ghe-status)- User wants to START work on new issue (use ghe-claim)- User wants to SAVE progress but CONTINUE working (use ghe-checkpoint)- User wants reports (use ghe-report)- User is not ready to END current phaseIMPORTANT: This CLOSES current thread and OPENS next thread. Use ghe-checkpoint if you just want to save progress without changing phases.EXAMPLES:<example>Context: DEV work complete,
github-elements-tracking
This skill should be used when the user asks to "track work across sessions", "create an epic", "manage issue waves", "post a checkpoint", "claim an issue", "recover from compaction", "coordinate multiple agents", "update memory bank", "store large documents", or mentions GitHub Issues as persistent memory, multi-session work, context survival, agent collaboration, SERENA MCP memory, or project-level context. Provides complete protocols for using GitHub Issues as permanent memory that survives context exhaustion, with integrated SERENA MCP memory bank for project-level context and large document storage.
markdown-toc
Use when generating or updating Table of Contents in markdown files. Supports multiple files, glob patterns, configurable header levels, and various insertion modes. Triggered by "generate toc", "update toc", "table of contents", "add toc to markdown".
marketplace-release
Use when creating releases for Claude Code plugin marketplaces. Supports independent plugin versioning - each plugin can be released separately. Triggered by "release", "bump version", "create release", "publish plugin".