بنقرة واحدة
git-conventions
MangoCode git commit format, branch naming, and PR checklist — auto-loaded as a dependency
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
MangoCode git commit format, branch naming, and PR checklist — auto-loaded as a dependency
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | git-conventions |
| description | MangoCode git commit format, branch naming, and PR checklist — auto-loaded as a dependency |
| triggers | ["commit message","branch name","pull request","open a pr","squash and merge"] |
This skill is loaded automatically as a dependency by other skills (e.g. rust-review).
It defines the commit and branch standards to apply during reviews and when creating commits.
Follow the Conventional Commits specification:
<type>(<scope>): <short summary>
[optional body — wrap at 72 chars]
[optional footer: BREAKING CHANGE, Closes #<issue>]
Allowed types:
feat — new feature or capabilityfix — bug fixrefactor — code restructure without behaviour changeperf — performance improvementtest — test additions or changesdocs — documentation onlychore — build, CI, dependency updatesstyle — formatting, no logic changeScope: the crate or module name, e.g. skill-discovery, coordinator, tools
Summary: imperative mood, lowercase, no trailing period, ≤ 72 chars
Examples:
feat(skill-discovery): add folder-based skill support with sub-files
fix(coordinator): prevent dependency cycle in skill resolver
refactor(system_prompt): inject skills into cacheable prompt section
<type>/<short-kebab-description>
Examples:
feat/skill-system-upgradefix/coordinator-cycle-detectionrefactor/prompt-cache-alignmentFeature branches target main. Use squash and merge on PR close.
Before marking a PR ready for review:
cargo check passes with zero warningscargo test passes for all affected cratescargo clippy -- -D warnings passes/// doc commentsWhen committing on behalf of a human, use their noreply GitHub email to avoid leaking personal information. Never hardcode personal email addresses in commit metadata.