Codex TopicLab Git Commit Conventions for PR Branches
Check local TopicLab rules before proposing a branch slug, Conventional Commit subject, and file scope. Preserve contributor and ownership context.
中文Install in Codex
Codex with a Tashan-TopicLab checkout, the target diff or commits, and applicable repository instructions.
- Copy the entire pinned `.codex/skills/git-commit-conventions/` directory to `.agents/skills/git-commit-conventions/` in the target checkout.
- Open Codex in that checkout and invoke `$git-commit-conventions` with the example task and desired output.
Example task
Invoke `$git-commit-conventions` for a practice TopicLab docs correction. Request a branch slug and an English subject draft.What to check
The branch and subject follow the local conventions, and the type reflects a documentation change. The draft identifies the files in scope.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should I include a scope?
Include the narrowest meaningful module or application name when the change clearly belongs there.