Loading...
Loading...
Found 361 Skills
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Creates context-aware git commits with smart pre-commit checks, submodule support, and conventional commit message generation. Use when user requests to commit changes, stage and commit, check in code, save work, save changes, push my code, finalize changes, add to git, create commits, run /commit command, or mentions "git commit", "commit message", "conventional commits", "stage files", "git add", or needs help with commits.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Generate Git branch names from staged or branch changes
Use when squash-merging a feature branch into main for linear history. Handles pre-flight checks, squash merge, commit delegation to git-commit, and branch cleanup.
Implement a single user story or task from a GitHub Issue backlog. Executes a single Ralph Loop iteration by fetching the next open issue, assigning it, implementing the code, creating a branch and PR, and moving on. You MUST use this skill when asked to "implement a user story", "run one iteration", "do the next task", "execute a ralph loop iteration", or "complete a task from the backlog".
Automated release pipeline that merges main, runs tests, performs pre-landing review, bumps version, updates changelog, creates bisectable commits, and opens a pull request. Use this skill when the user says "ship it", "ship this", "release this", "prepare for release", "open a PR", "push and PR", "land this", "get this ready to ship", "create release", "/ship-workflow". Handles the full lifecycle from pre-flight checks through PR creation.
Archive completed changes and merge specification differences into permanent documents. Used when changes have been deployed, are ready for archiving, or when specifications need to be updated after implementation. Trigger words include "openspec archive", "archive", "archive proposal", "merge specifications", "complete proposal", "update documents", "finalize specifications", "mark as completed".
Opens a pull request for a small jackin' change with the correct body shape and auto-selected verify-locally blocks. Use when the operator runs /jackin-dev:create-pr.
This skill should be used when the user wants to publish a package to npm, bump a version, release a new version, or mentions "npm publish", "bun publish", "version bump", or "release". Handles changelog updates, git push, and npm publishing with OTP authentication.
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.