Loading...
Loading...
Found 696 Skills
Write git commit messages in Angelo Laus's Conventional Commits style (type(scope): lowercase imperative subject, plus a terse "- add/replace/cover" bullet body). Use whenever the user asks for a commit message, shows a diff or staged changes, or says "commit this". Output the message only. Never run git commit.
Multi-person projects - shared state, todo claiming, handoffs
Generate conventional commit messages based on git diff analysis. Use when you need to create well-structured commit messages following conventional commit format.
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.
Generate concise, descriptive git commit messages following best practices. Use when creating git commits from staged changes, crafting commit messages, or reviewing commit message quality. Use when the user says /commit or asks to create a git commit.
Open a draft pull request on GitHub. MUST use when you want to create/open a PR.
Push branch and create GitHub pull request (auto-assigned)
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git.
Create a pull request following project conventions
Use when creating git commits in this project
Summarize current work, commit, push, and create or update a PR. Automatically write conversation context into the PR description to ensure reviewers can quickly understand the background.
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.