Loading...
Loading...
Found 409 Skills
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
Analyze an in-progress git branch, compare it with the current master/main using a subagent, derive practical lessons, and generate a concise redo handoff. Use when restarting a messy branch, redoing work cleanly, extracting lessons from current changes, or preparing another agent to verify the handoff, align with the user, and rebuild from the default branch.
Open a pull request for the current feature
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Work with Git repositories from the command line.
This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix for a production issue.
Methodology for effective AI-assisted software development. Use when helping users build software with AI coding assistants, debugging AI-generated code, planning features for AI implementation, managing version control in AI workflows, or when users mention "vibe coding," Cursor, Windsurf, or similar AI coding tools. Provides strategies for planning, testing, debugging, and iterating on code written with LLM assistance.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
Use to manage brand guidelines, approvals, and ongoing refresh cadence.
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
Git version control with branching, merging, and rebasing. Use for source control.
Write detailed Conventional Commit messages using only the active chat conversation as context. Use when the user asks for commit messages based on discussion history, requests module-scoped commit subjects, or explicitly forbids checking git logs, diffs, or code files.