Loading...
Loading...
Found 42 Skills
Safely clean merged and stale git branches with explicit confirmations.
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
Generate a language translation for a mkdocs documentation stack.
Create and checkout a new git branch with smart validation and GitHub issue integration
Start working on a Marshroom cart issue — creates branch, injects context, updates status to running
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Standard flow from any task source (link or description) to creating a PR: resolve task, create branch and TODO.md, wait for fixes, create PR against origin only. Use find-skills to discover data-source query methods; after confirmation save to global config so the discovery step can be skipped next time. Use when the user provides a task link/description, asks to 'follow GitHub workflow', or 'create PR from task'.
Create or update pull requests for the current branch
Push branch and create GitHub pull request. Use when the user wants to open a PR, submit changes for review, or push and create a pull request.
Create a PR with dev as base using the pull request template. Use when opening a new PR.