القائمة
Conventional Commits message generation rules. Referenced by other skills.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Set up the development environment with all required tools and dependencies
Stage changes and create a Conventional Commits compliant commit
Create a feature branch and implement changes based on a GitHub issue or text instruction
Linter and formatter command reference table by file extension. Referenced by other skills.
Run all linters and formatters with auto-fix, then report results
Push committed changes and create or update a pull request
| name | commit-conventions |
| description | Conventional Commits message generation rules. Referenced by other skills. |
Follow Conventional Commits 1.0.0 (enforced by commitlint).
This is a reference skill. It is not invoked directly by the user; other skills read this file when generating commit messages.
| Change | Type |
|---|---|
| New feature | feat |
| Bug fix | fix |
| Documentation only | docs |
| Formatting (no behavior change) | style |
| Refactoring | refactor |
| Performance improvement | perf |
| Adding or updating tests | test |
| Build system or dependencies | build |
| CI/CD configuration | ci |
| Other | chore |
When changes are concentrated in a specific directory, add a scope:
infra/ -> (infra)scripts/ -> (scripts).github/workflows/ -> (ci).agents/skills/ -> (skills)If src/ has subdirectories, use a more specific scope. If changes span multiple directories, omit the scope.
type[(scope)]: description (target 50 characters)! after the type (e.g., feat!: remove legacy api).env files (exclude from git add)Co-Authored-By to commit messages (personal project)