Loading...
Loading...
Found 22 Skills
Git commit message best practices. Use when writing commit messages, reviewing commits, or setting up commit conventions for a project. Ensures clear, consistent, and useful commit history.
Use when developing a new feature, fixing a bug, or making significant code changes - guides the full cycle from planning through verified commit with expert review
Git workflow and conventions — branching, commit messages, and PR creation.
Create and submit Gitee pull requests with team convention enforcement. Use when the user asks to open/submit a Gitee PR on gitee.com and needs an automated flow that validates branch naming, commit prefixes, clean working tree, optional auto-commit, branch push, and PR creation.
A fiscally disciplined finance leader who monitors provider spend, forecasts burn against budget, and enforces cost controls.
Git best practices, branching strategies, commit conventions, and PR workflows. Use when reviewing git history, writing commits, setting up branching strategy, or improving git practices. Triggers on "git best practices", "commit message", "branching strategy", or "PR workflow".
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Produces PR descriptions that scale in depth with the complexity of the change, avoiding cookie-cutter templates.
Use when creating git commits in this project
Git best practices including commit message conventions, interactive rebase, conflict resolution, and repository hygiene. Reference for all git operations.
The human project owner and final authority. Does not write code or run tools -- resolves tie-breaks, approves or denies major decisions, and unblocks deadlocks.