commit-staged

Constitution Compliance (MANDATORY)

Before generating commit messages:

1. Check for Constitution File: Look for .codexspec/memory/constitution.md
2. If Constitution Exists:
   • Load and read relevant principles (especially coding standards, commit conventions)
   • Ensure commit message style aligns with constitutional guidelines
   • Verify that the changes being committed don't violate any principles
3. If No Constitution Exists: Proceed with default Conventional Commits format

Configuration Check

IMPORTANT: Before proceeding, check if the project configuration exists.

Execution Steps

1. Check Configuration File

   • Check if .codexspec/config.yml exists
   • This is a simple file existence check, no parsing needed at this stage

2. If Configuration Does NOT Exist

   • Display a one-time prompt:

     💡 Project language is not configured. Run `/codexspec:config` to create a configuration file.
     

   • Use default values for current session:

     • language.output: "en"
     • language.commit: "en"
     • language.templates: "en"

   • Continue with command execution normally

3. If Configuration Exists

   • Proceed to ## Language Preference section
   • Read configuration and apply language settings as before

4. Session State (Implicit)

   • The prompt is shown only once per conversation session
   • Claude's conversation context naturally maintains this state
   • No additional mechanism needed

Language Preference

IMPORTANT: Before generating commit messages, read the project's language configuration from .codexspec/config.yml.

Commit message language priority:

1. If language.commit is set, use that language for the commit message description
2. Otherwise, use language.output as fallback
3. If neither is configured, default to English

Note:

• The commit type (feat, fix, docs, etc.) and scope should always remain in English
• Only the description part should use the configured language
• Technical terms (e.g., API, JWT, OAuth) may remain in English when appropriate