Loading...
Loading...
Found 14 Skills
Commit message format, logical grouping, and branch naming rules. Follow when creating git commits, branches, or PRs.
Git Commit Rules
Create semantic git commits following best practices and Conventional Commits specification.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Generate release notes from commits since last tag
Review code changes against a plan using the plan location and implementing git commit(s).
Creates Checkmk werks (changelog entries) from git commits
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.