Loading...
Loading...
Found 19 Skills
Git Commit Specification, covering commit message format (feat/fix/refactor), Issue linking, branch naming, PR submission preparation, and rebase usage. Used when users submit code, write commit messages, create branches, or prepare PRs.
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing.
Branch naming conventions, Git Flow vs trunk-based development, feature branch lifecycle, and release strategies. Reference when creating branches, planning releases, or choosing a branching model.
Guide for using git according to my preferences. Use it when you're asked to commit something.
Prepare local GitHub issue branches from the repository default branch using GitHub-style issue branch names. Use when starting issue-linked work, when the user says new branch for an issue, or when an agent must move onto the correct issue branch before implementation.
Create alpha-forge git worktrees with auto branch naming. TRIGGERS - create worktree, new worktree, alpha-forge worktree.
Define and manage Git workflow rules in docs/rules/git/. Use when establishing commit message formats, branch naming conventions, PR requirements, code review standards, or any Git-related enforceable rules.
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
Reference for Domestic Git Platform Configuration - Differences in SSH/HTTPS/Credentials/CI Integration and Mirror Sync Configuration for Gitee, Coding.net, Jihu GitLab, and CNB. Only invoke when the user explicitly uses /chinese-git-workflow; do not trigger automatically based on context.
Create git commits following Conventional Commits specification with project-specific branch naming rules
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Git workflow guidance for commits, branches, and pull requests