serialized-build-commands
Agents should invoke this skill before running build, test, lint, or format commands that use shared caches, file locks, build directories, or package manager state. Use especially before Rust Cargo commands such as cargo check, cargo test, cargo clippy, cargo fmt, cargo build, or any shell command containing cargo.
- License 许可
- MIT
- 最近更新
- 2026-10-31
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- serialized-build-commands
- description
- Agents should invoke this skill before running build, test, lint, or format commands that use shared caches, file locks, build directories, or package manager state. Use especially before Rust Cargo commands such as cargo check, cargo test, cargo clippy, cargo fmt, cargo build, or any shell command containing cargo.
03 SKILL.md 正文
Serialized Build Commands
Use this skill to avoid corrupting or blocking project validation by batching commands that share locks or build state.
Cargo Rule
When a command contains cargo or cargo.exe:
- Emit at most one tool call containing Cargo in a single assistant response.
- Put exactly one Cargo invocation in that shell command.
- Wait for the tool result before deciding the next Cargo command.
- Inspect the result before continuing.
- Do not run Cargo commands in parallel.
- Do not combine Cargo commands with
&&,;,&,wait,xargs, shell loops, subshell batching, or multiple tool calls in the same assistant response. - Do not start another Cargo command while one is still running.
If multiple Cargo checks are required, run them as separate turns:
- Run one Cargo command.
- Read the result.
- Decide whether the next Cargo command is still needed.
- Run the next Cargo command in a later assistant response.
Lock Or Timeout Handling
If Cargo reports a file lock, blocked build directory, timeout, or interrupted command:
- Stop launching new Cargo commands.
- Inspect the process and repository state.
- Prefer the smallest focused command that verifies the specific failure after the blockage is resolved.
- Report a blocker if the lock cannot be resolved safely.
Other Build Tools
Apply the same serialization rule to other tools when project lessons, logs, or failures show shared-state contention:
npm,pnpm,yarn,bunpytest,uvmake,cmake,ninja- language-specific build or test runners with shared caches
Project instructions and LessonsLearned can make any of these rules stricter. Follow the stricter rule.
04 同仓库更多 Skills
serialized-build-commands
Agents should invoke this skill before running build, test, lint, or format commands that use shared caches, file locks, build directories, or package manager state. Use especially before Rust Cargo commands such as cargo check, cargo test, cargo clippy, cargo fmt, cargo build, or any shell command containing cargo.
submit-epic
Use when the user asks Pi to submit, create, or draft a new HEPHA EPIC directly from a registered project workspace, preserving the useful legacy DevCycle MCP submit-epic command, for example "submit-epic for HEPHA build observability projection hooks" or "create a HEPHA EPIC titled Runtime Approval Gates".
start-feature
Use when the user asks Pi to start a HEPHA FEAT implementation, run start-feature, or run start-implementing for a READY FEAT from a registered project workspace, for example "use the start-feature skill for FEAT-003".
refine-feature
Use when the user asks Pi to run refine-feature, refine a HEPHA FEAT, create FeatureTasks and phase files, or move a clarified FEAT to Ready To Develop, for example "refine-feature FEAT-004" or "Use the refine-feature skill for HEPHA FEAT-004".
design-feature
Use when the user asks Pi to run design-feature, design a HEPHA FEAT, create UI requirements, or prepare UX/design artifacts for a FEAT, for example "design-feature FEAT-004" or "Use the design-feature skill for HEPHA FEAT-004".
deep-dive
Use when the user asks Pi to run a HEPHA Deep-Dive for an EPIC or FEAT, gather Deep-Dive questions, or apply saved Deep-Dive answers to a MemoryBank document, for example "use the deep-dive skill for HEPHA FEAT-004".