Loading...
Loading...
Found 347 Skills
This skill should be used when the user wants to create a pull request, or submit code for review. Triggers on "push a PR", "create a PR", "open a pull request", "make a PR", "submit for review".
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.
AntiGravity Start Work/Finish Work/New Project Initialization Process. Loaded when saying 'Start Work', 'Finish Work', or 'Initialize Project'.
User guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
Crear un proyecto nuevo fusionando una plantilla del equipo según el stack tecnológico (Angular, React, Symfony, etc.). Usar siempre que el usuario pida crear un proyecto nuevo, inicializar desde plantilla, o use `/project-create`. Si el stack no está claro, preguntar antes de cualquier acción.
Applicable when you need to resolve ongoing git merge/rebase conflicts.
Opens a pull request for a small jackin❯ change with the correct body shape and auto-selected verify-locally blocks.
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Sync with remote repository using pull --rebase. Use when you need to update your local branch with remote changes.
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.