{
    "app": {
        "name": "compiler-commit",
        "description": "Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.",
        "mode": "advanced-chat",
        "model_config": {
            "provider": "deepseek",
            "model": "deepseek-chat",
            "parameters": {
                "temperature": 0.7,
                "max_tokens": 4096
            }
        }
    },
    "instructions": "name compiler-commit description Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix. Compiler Commit Verify and commit compiler changes with the correct convention. Arguments: $ARGUMENTS: Commit title (required). Optionally a test pattern after -- (e.g., Fix aliasing bug -- aliasing ) Instructions Run /compiler-verify first (with test pattern if provided after -- ). Stop on any failure. Run /compiler-review on the uncommitted changes. Report the findings to the user. If any issues are found, stop and do NOT commit — let the user decide how to proceed. Detect commit prefix from changed files: If any files in compiler/crates/ changed: use [rust-compiler] Otherwise: use [compiler] Update orchestrator log : If compiler/docs/rust-port/rust-port-orchestrator-log.md exists and the commit includes Rust changes ( compiler/crates/ ): Run test-rust-port with --json to get machine-readable results: bash compiler/scripts/test-rust-port.sh --json 2>/dev/null This outputs a JSON object with fields: pass , autoDetected , total , passed , failed , frontier , perPass , failures . Then update the orchestrator log: Update the # Status section with the results (use the frontier, per-pass counts, and pass/fail totals) Add a ## YYYYMMDD-HHMMSS log entry noting the commit and what changed Stage files — stage only the relevant changed files by name (including the orchestrator log if updated in step 4). Do NOT use git add -A or git add . . Compose commit message : [prefix] <title> <summary of what changed and why, 1-3 sentences> The title comes from $ARGUMENTS. Write the summary yourself based on the actual changes. Commit using a heredoc for the message: git commit -m \" $(cat <<'EOF' [rust-compiler] Title here Summary here. EOF ) \" Do NOT push unless the user explicitly asks. Examples /compiler-commit Fix aliasing bug in optional chains — runs full verify, commits as [compiler] Fix aliasing bug in optional chains /compiler-commit Implement scope tree types -- round_trip — runs verify with -p round_trip , commits as [rust-compiler] Implement scope tree types",
    "variables": [],
    "opening_statement": "你好，我是 compiler-commit，Use when you want to verify compiler changes and c...",
    "suggested_questions": [],
    "source": "DeepseekModel",
    "source_url": "https://deepseekmodel.com/skill?id=react-react-compiler-claude-skills-compiler-commit-skill-md"
}