execute-task
Implements one task in an isolated git worktree following TDD. Creates commits for implementation and fixes, invokes independent verification.
Implements one task in an isolated git worktree following TDD. Creates commits for implementation and fixes, invokes independent verification.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
Fetch a GitHub issue and generate a plan to resolve it
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Merges completed task worktree to main branch. Handles sequential merge queue to prevent conflicts.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Create and manage per-task isolated git clones (sandboxes) for Codex CLI sessions, with automatic branch creation and safety hooks that block committing/pushing on main/master. Use when running multiple Codex sessions or parallel tasks and you want to avoid git worktree friction, cwd/branch mixups, or environment collisions.
Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.
Strategic patterns for codebase exploration using Gemini's large context window. Covers token thresholds, model routing, and exploration strategies. Use when deciding between Claude and Gemini for exploration, analyzing large codebases, or choosing between Flash and Pro models for context size.
Use when designing standardized development workflows, paved roads, or opinionated defaults. Covers golden path patterns, template design, developer workflow optimization, and guardrails.
Set up Git worktrees for agent parallelization with isolated environments. Use when setting up parallel agent execution, creating isolated environments per agent, or enabling concurrent development workflows.
create git worktree with new branch. use when working on features in parallel, isolating experimental work, or avoiding stash/switch overhead. creates sibling directory.
Perform a shallow clone of a Git repository to a temporary location.
Read context from GitHub issue including body and comments. Use before starting implementation work or when prior context is needed.
Create isolated git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create changelog from git commits. Use when preparing release notes.
Use when writing or improving messages for Git commits, or when asked to generate a commit message or pull request description.
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
reimplement current branch with clean, narrative-quality git commit history. use when commit history is messy, after exploratory work, or before PR review. creates new branch with logical, atomic commits.