langadventurellc/claude-marketplace

Commits staged and unstaged changes to git with a concise conventional commit message. Use when changes are ready to be committed, after completing a task, or when the user asks to commit.

This skill should be used when the user asks to create Trellis issues including "create a project", "create epics", "create features", "create tasks", "new project", "new epic", "new feature", "new task", "break down project into epics", "break down epic into features", "break down feature into tasks", "decompose project", "decompose epic", "decompose feature", or mentions creating any type of issue in Trellis.

Orchestrates issue creation with automatic review. Use when asked to "create and review issues", "create verified issues", or when you want issues automatically validated against requirements.

Verifies Trellis issues against original requirements for completeness, correctness, and appropriate scope. Use when asked to "verify issue", "validate trellis issue", "check issue completeness", or "review created issue".

This skill should be used when the user asks to "implement task", "claim task", "work on task", or mentions implementing a single task in Trellis. For features, epics, or projects, use issue-implementation-orchestration instead.

This skill should be used when the user asks to "create implementation plan", "plan the implementation", "detailed plan", "file-by-file plan", or mentions needing a comprehensive implementation plan before coding. Creates detailed file-by-file implementation plans by researching the codebase and outputting specific changes needed.

Reviews code changes from a completed task implementation for correctness, completeness, and simplicity. Use when asked to "review implementation", "review task code", "code review", "verify implementation", or after completing an issue implementation.

Helps users transform vague ideas into well-defined requirements documents. Use when a user has a change they want to make to the codebase but hasn't fully articulated what they need. Works conversationally to extract and clarify requirements, scaling depth to the complexity of the work.

Performs technical research and analysis without implementation. Use when asked to "analyze this", "research this change", "investigate", "what would be involved", "where would changes occur", "scope this work", "technical discovery", or before creating complex Trellis issues to understand the technical landscape.