Verified:GitHub

github-commit

Enforces commit message and pull request conventions for GitHub workflows.

Updated Aug 14, 2026

Search Tags:#git #code review #version control #pull request #github #commit message

One-click install

npx skills add https://github.com/MDSIXONE/opencode-config --skill github-commit-mdsixone

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: github-commit
Source: https://github.com/MDSIXONE/opencode-config/tree/main/skills/github-commit
Command: npx skills add https://github.com/MDSIXONE/opencode-config --skill github-commit-mdsixone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent commit messages and incomplete pull request descriptions make code history hard to follow and reviews slow. This Skill standardizes how commits and PRs are written whenever you ask the AI to commit code or create a pull request. ## Core Features & Use Cases - Commit Message Convention: Generates Chinese Emoji-prefixed commit subjects in the form `Emoji 范围：简短动作`, with one coherent change per commit. - Pull Request Guidelines: Ensures PRs explain affected sections, safety implications, validation steps, linked issues, and layout screenshots when needed. - Use Case: After finishing a navigation path-planning fix, ask the AI to commit the change and it produces a message like `🧭 导航：优化目标点路径规划`, then drafts a PR covering impact, safety, and validation. ## Quick Start Ask the AI to commit the current changes and create a pull request following the repository's commit guidelines.

Frequently Asked Questions about github-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a standardized commit message for GitHub?▼

Use the format `Emoji 范围：简短动作`, such as `🧭 导航：优化目标点路径规划`. Each commit should contain exactly one coherent change so the history stays readable and easy to revert.

What should a good pull request description include?▼

A pull request should explain the affected sections, safety implications, validation performed, and linked issues. Include layout screenshots when the change affects the user interface.

When does this commit convention skill activate?▼

It activates only during git commit or GitHub submission workflows, such as writing commit messages, pushing code, or creating pull requests. It does not affect other coding tasks.

Can I combine multiple changes into one commit?▼

No, the guidelines require one coherent change per commit. Split unrelated modifications into separate commits so each one can be reviewed, reverted, or cherry-picked independently.