Loading...
Loading...
Found 127 Skills
Draft, rewrite, and validate Odoo-style commit messages using [TAG] module: summary format, 50/72 length limits, imperative English, WHY-first body, and correct tag selection. Includes optional migration tagging ([MIG]) when the project workflow (like OCA) uses it.
Generate clear, conventional commit messages from staged changes. Use when the user asks to commit or needs a commit message.
Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Review full Git working tree changes and propose one or more safe, reviewable commit messages plus commit ordering. Use when the user asks for "git propose", asks how to split current changes into commits, or wants Conventional Commit messages from staged, unstaged, and untracked changes.
Review local git changes and perform a light code review. If no issues are found, commit the changes. Does NOT write or modify code — only reviews and commits. Optionally accepts a commit message header as an argument.
Expertise in structured Git commit workflow with Chinese team conventions. Use this skill when the user asks to "commit", "提交", "stage", "暂存", "show status", "git status", or any variant related to managing git changes. The user does NOT need to explicitly mention "git-commit-workflow" - ANY request to commit changes or manage git state should automatically trigger this skill. Handles automatic commit message generation with PMS and GitHub Issue tracking, following strict 80-character line limits.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Helps users create standardized Git commits. Use this when users want to submit code, save changes, or create a commit.
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
Analyze staged Git changes and generate a concise Chinese commit message that follows repository commit style. Use when the user asks to commit code, generate a commit message, or summarize staged changes into a Chinese Git commit title and bullets.