Loading...
Loading...
Found 487 Skills
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.
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
Complete development with structured merge/PR options. Use when ready to merge or submit work.
Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.
Sync with remote repository using pull --rebase. Use when you need to update your local branch with remote changes.
Stage all changes, commit, and push. Use when user asks to "ship", "commit and push", "add all and push", or requests staging all changes, committing, and pushing.
Stabilizes a software project by repeatedly running and testing it in a loop, fixing any issues.
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.