Loading...
Loading...
Found 155 Skills
Workflow Specifications Adapted to Domestic Git Platforms and Team Habits - Full Coverage of Gitee, Coding, Jihu GitLab
Create Git commits with Conventional Commits analysis, safe staging, and concise message generation. Use when the user asks to commit changes or create a git commit.
Use version control as a craft — atomic commits, buildable history, useful PRs, bisect-friendly main, recoverable mistakes. Use this skill whenever the task involves writing commits or PRs, choosing a branching model, deciding rebase vs. merge, recovering from a force-push or accidentally-committed secret, debugging a regression with `git bisect`, structuring a long change as a series of small reviewable steps, or judging whether a repo's history is readable. Use it especially when reviewing commit messages, PR descriptions, branching strategies, or merge policies. Built on Tim Pope and Chris Beams on commit messages, Paul Hammant on trunk-based development, Vincent Driessen on GitFlow (and his 2020 note retiring it for SaaS), Linus Torvalds on never rebasing public commits, and the Google Engineering Practices CL guide.
Create atomic user-approved commits with `feat`/`fix`/`chore` titles and finalise branch merge/cleanup with tracking sync. Triggers: commit changes, split commits, finalise branch, commit message.
Git Commit Workflow
Conventional Commits v1.0.0 standards for git messages. Use when (1) creating git commits, (2) writing or drafting commit messages, (3) reviewing commit message format, (4) explaining commit conventions, or (5) validating commit message compliance.
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Generate well-formatted git commit messages following conventional commit standards
Perform git commit following Conventional Commits standards
Generate feature-based and confidentiality-safe English LinkedIn Experience drafts directly from commit messages. Use when asked to write LinkedIn experience text from real commit activity for all-time or a specific date range (`since`/`until` in YYYY-MM-DD), while avoiding repository statistics and internal/confidential implementation details.
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Git version control and GitHub CLI workflows for commits, branches, pull requests, and code reviews with professional commit message practices.