القائمة
Optimization guide for the commit-pro commit workflow. Documents how to keep the plugin authoritative and reduce token usage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation. Modes: --auto (default), --manual, --skip-elicit
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD. Use when: an expert agent needs to self-review and self-correct code after the Execute phase, before sniper validation.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing. Do NOT use for: lint/type/code-quality validation (use code-quality / sniper AFTER functional verification passes).
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use when committing changes, saving work, staging and committing, or choosing a conventional commit message.
Use when committing, branching, opening PRs, or deciding merge strategy. Covers GitHub Flow (default), trunk-based, branch naming conventions, squash vs rebase, branch lifecycle, and protected branch enforcement.
Universal post-commit actions. CHANGELOG update for all repos (git tag is created POST-MERGE, not here — see `commit` command Step 8). Plugin version bumping for marketplace repos. Triggered after any code commit (except wip/amend/undo).
| name | commit-optimization |
| description | Optimization guide for the commit-pro commit workflow. Documents how to keep the plugin authoritative and reduce token usage. |
commit-pro ships its own comprehensive git workflow (branch flow, security gate, conventional commits, post-merge tagging) that supersedes any generic git guidance a host runtime injects. Keeping the plugin as the single source of truth for git operations avoids duplicated/contradictory instructions and reclaims context tokens.
~/.codex/config.toml, let the commit-pro plugin own commit/PR behavior; do not
restate generic commit or PR conventions in AGENTS.md.AGENTS.md documents its own commit conventions, make sure they
do not contradict commit-pro's flow (protected-branch enforcement, PATCH-only bumps,
post-merge tagging).commit flow (the commit agent),
never a bare git commit outside its steps — that is what guarantees the security
gate, branch-protection check, and CHANGELOG/version bump actually run.Treating commit-pro as the authority — and removing redundant built-in git guidance where the runtime allows — is the whole optimization: one consistent workflow, fewer tokens, no drift.