Loading...
Loading...
Found 20 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.
Write changelog entries for open source documentation sites using Keep a Changelog format. Use when asked to "write a changelog", "update the changelog", "add changelog entry", "document recent changes", or after a release/set of changes that should be recorded. Reviews git commits since the last changelog entry and produces a categorized, human-readable entry.
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
Generate release notes from commits since last tag
List recent git commits that are linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", or wants a list of commits with their session context.
Creates Checkmk werks (changelog entries) from git commits
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
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.