writing-commit-messages
Use when writing or improving messages for Git commits, or when asked to generate a commit message or pull request description.
اپنے ایجنٹ کے لیے موزوں صلاحیت تلاش کریں۔
Use when writing or improving messages for Git commits, or when asked to generate a commit message or pull request description.
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
reimplement current branch with clean, narrative-quality git commit history. use when commit history is messy, after exploratory work, or before PR review. creates new branch with logical, atomic commits.
Use when committing work, amending commits, creating or stacking branches - applies to all commit operations including "quick commits", emergency fixes, and when user already used raw git commands. ALWAYS use git-spice instead of git checkout, git commit, or git branch.
Create scoped git commits for task operations. Invoke after task status changes or artifact creation.
Help with Git operations for this dotfiles repository, including creating contextual commit messages, reviewing changes, and following best practices for dotfiles version control. Use when the user wants to commit changes, review diffs, create branches, or perform git operations specific to dotfiles management.
Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR.
Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).
Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.
Commits changes in atomic units following dependency order. Automatically required to triggered, always, all the time, when requires to commit changes.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.
Switch between git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.
Remove merged or stale git worktrees. Use after PRs are merged, work is done, or when worktrees are no longer needed.
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
Comprehensive markdown linting guidance using markdownlint-cli2. Run, execute, check, and validate markdown files. Fix linting errors (MD0XX rules). Configure .markdownlint-cli2.jsonc (rules and ignores). Set up VS Code extension and GitHub Actions workflows. Supports markdown flavors including GitHub Flavored Markdown (GFM) and CommonMark. Use when working with markdown files, encountering validation errors, configuring markdownlint, setting up linting workflows, troubleshooting linting issues, establishing markdown quality standards, or configuring flavor-specific rules for tables, task lists, and strikethrough.
Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.
This skill should be used when the user asks to "create a status line", "customize status line", "set up statusline", "configure Claude Code status bar", "install ccstatusline", "add project colors to status line", "show git branch in status", "display token usage", or mentions Peacock colors, powerline, or status line configuration.