execute
Use when the user wants to execute tasks autonomously, run compounder on a tasks.md file, start autonomous development, compound through a task list, or implement tasks iteratively. Guides autonomous task execution using compound loops.
init
Initialize a new feature workflow with git worktree. Use when the user wants to start a new feature, create an isolated development branch, says "init worktree", or needs to set up a feature branch for compounder workflow.
orchestrate
Main workflow orchestrator for complex tasks. Coordinates phase transitions, enforces checkpoints based on config, manages subagent delegation. Invoke for [COMPLEX] tasks.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
github-navigator
GitHub operations via gh CLI. Uses built-in help to discover commands dynamically. Covers files, directories, issues, PRs, releases, actions, and everything else. CRITICAL: Always use this skill instead of webfetch for GitHub URLs.
team-workflows
Team collaboration patterns - shared configs, standards, onboarding
git-workflows
Guide for git operations with Claude Code. Commits, PRs, code review, branch management, and best practices. Use when committing changes, creating pull requests, reviewing code, or managing branches.
monorepo-patterns
Monorepo workflows - navigation, cross-package changes, tooling
creating-hooks
Guide for implementing Claude Code hooks. Use when creating event-driven automation, auto-linting, validation, or context injection. Covers all hook events, matchers, exit codes, and environment variables.
custom-slash-commands
Guide for creating custom Claude Code slash commands - shortcuts for frequently-used prompts and workflows. Use when creating reusable prompts, automating common tasks, or building team workflows. Covers frontmatter, arguments, bash execution, and namespacing.
issue-prerequisite
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
work-intake
Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.
session-start
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
pr-creation
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
autonomous-orchestration
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
autonomous-operation
Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved
issue-lifecycle
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
Page 2 of 31 · 543 results