683 skills · sorted by relevance
Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.
Manage version control through GitButler’s but CLI. Select files or hunks, meaning sections of a diff, for commits; organize dependent branches, split or combine history, resolve conflicts, and create pull requests using task-specific command workflows.
Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.
Undo development changes recorded by GSD using Git revert. Select recent commits or target an entire phase or plan, with dependency checks and confirmation before the rollback runs.
Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.
Plan and implement features with a workflow that adapts to their complexity. It connects testable requirements to tasks, tests, and small commits, then checks the finished work against the specification through an independent verification pass.
Review Git changes and draft commit messages using Conventional Commits, a format that labels the type and scope of a change. Produce concise subjects, explanatory bodies, and issue or breaking change references when needed.
Polish Korean commit messages drafted by AI into natural developer language. The skill removes stiff wording and literal translations while preserving the stated changes, commit type, scope, issue numbers, and code identifiers.
Apply the project's rules for commit messages, branch names, and bug fixes. The skill also points agents to bundled documentation and requires regression tests, which check that a fixed bug does not return.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.
The English summary is being prepared. Showing the original description.
Triages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.
The English summary is being prepared. Showing the original description.
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Find and identify the CBasePlayerPawn::CommitSuicide virtual function's vtable slot in the CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering server.dll or libserver.so to locate the self-inflicted-death handler (used by the "kill"/bot_kill console commands and related gameplay code) by RTTI-walking CBasePlayerPawn's primary vtable and reading its known slot index directly, then confirming the body matches CommitSuicide(bool bExplode, bool bForce) semantics. Trigger: CBasePlayerPawn_CommitSuicide
The English summary is being prepared. Showing the original description.
Review how easy code is to maintain using CodeScene MCP. Compare structural health scores before and after edits, identify design issues, and check commits and pull requests for changes that reduce maintainability.
Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.
Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.
Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.
Find unused TypeScript code, verify references with a language server, and assign removals to parallel agents. Group changes by file, create separate commits, and check types, tests, and the build after cleanup.