compiler-commit
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.
DeepseekModel
Curated skill
Quality Excellent · 90
v1.0.0
Get
https://deepseekmodel.com/api/download.php?id=react-react-compiler-claude-skills-compiler-commit-skill-md&format=skill
Download .skill
Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
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
Keywords that activate this skill. Click one to copy it.
This skill does not provide trigger words.
The downloaded .skill package contains the following fields.
| Field | Description |
|---|---|
| format | Format tag (skill/v1) |
| skill_id | Unique skill ID |
| name | Skill name |
| version | Version |
| description | Description |
| category | Categories (array) |
| trigger_words | Trigger words |
| tags | Tags |
| source | Source |
| source_url | Source URL (this page) |
| exported_at | Exported at (set per download) |
| system_prompt | System prompt body |
| model_config | Model config: provider / model / temperature / max_tokens / top_p |
| examples | Examples |
| install_guide | Import guide for Coze / Dify / Claude / custom frameworks |
The same skill can be exported in different platform formats.
