[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C6Q3EYVT92A4VM4FF4M120":3,"skill-same:01M7C6Q3EYVT92A4VM4FF4M120":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C6Q3EYVT92A4VM4FF4M120","serialized-build-commands",null,"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.","aboimpinto\u002FAgenticDevelopmentProcess","aboimpinto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1231687?v=4","01M7C6P0WDWM5B2RBSKSPR66PZ","Paulo Aboim Pinto","01M7C6P0WXGYZP7QMFS91N8C3P",0,"MIT","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-companion\u002Fskills\u002Fserialized-build-commands\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: serialized-build-commands\ndescription: 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.\n---\n\n# Serialized Build Commands\n\nUse this skill to avoid corrupting or blocking project validation by batching commands that share locks or build state.\n\n## Cargo Rule\n\nWhen a command contains `cargo` or `cargo.exe`:\n\n- Emit at most one tool call containing Cargo in a single assistant response.\n- Put exactly one Cargo invocation in that shell command.\n- Wait for the tool result before deciding the next Cargo command.\n- Inspect the result before continuing.\n- Do not run Cargo commands in parallel.\n- Do not combine Cargo commands with `&&`, `;`, `&`, `wait`, `xargs`, shell loops, subshell batching, or multiple tool calls in the same assistant response.\n- Do not start another Cargo command while one is still running.\n\nIf multiple Cargo checks are required, run them as separate turns:\n\n1. Run one Cargo command.\n2. Read the result.\n3. Decide whether the next Cargo command is still needed.\n4. Run the next Cargo command in a later assistant response.\n\n## Lock Or Timeout Handling\n\nIf Cargo reports a file lock, blocked build directory, timeout, or interrupted command:\n\n- Stop launching new Cargo commands.\n- Inspect the process and repository state.\n- Prefer the smallest focused command that verifies the specific failure after the blockage is resolved.\n- Report a blocker if the lock cannot be resolved safely.\n\n## Other Build Tools\n\nApply the same serialization rule to other tools when project lessons, logs, or failures show shared-state contention:\n\n- `npm`, `pnpm`, `yarn`, `bun`\n- `pytest`, `uv`\n- `make`, `cmake`, `ninja`\n- language-specific build or test runners with shared caches\n\nProject instructions and LessonsLearned can make any of these rules stricter. Follow the stricter rule.\n","# Serialized Build Commands\n\nUse this skill to avoid corrupting or blocking project validation by batching commands that share locks or build state.\n\n## Cargo Rule\n\nWhen a command contains `cargo` or `cargo.exe`:\n\n- Emit at most one tool call containing Cargo in a single assistant response.\n- Put exactly one Cargo invocation in that shell command.\n- Wait for the tool result before deciding the next Cargo command.\n- Inspect the result before continuing.\n- Do not run Cargo commands in parallel.\n- Do not combine Cargo commands with `&&`, `;`, `&`, `wait`, `xargs`, shell loops, subshell batching, or multiple tool calls in the same assistant response.\n- Do not start another Cargo command while one is still running.\n\nIf multiple Cargo checks are required, run them as separate turns:\n\n1. Run one Cargo command.\n2. Read the result.\n3. Decide whether the next Cargo command is still needed.\n4. Run the next Cargo command in a later assistant response.\n\n## Lock Or Timeout Handling\n\nIf Cargo reports a file lock, blocked build directory, timeout, or interrupted command:\n\n- Stop launching new Cargo commands.\n- Inspect the process and repository state.\n- Prefer the smallest focused command that verifies the specific failure after the blockage is resolved.\n- Report a blocker if the lock cannot be resolved safely.\n\n## Other Build Tools\n\nApply the same serialization rule to other tools when project lessons, logs, or failures show shared-state contention:\n\n- `npm`, `pnpm`, `yarn`, `bun`\n- `pytest`, `uv`\n- `make`, `cmake`, `ninja`\n- language-specific build or test runners with shared caches\n\nProject instructions and LessonsLearned can make any of these rules stricter. Follow the stricter rule.\n",{"name":5,"description":7},"master","57a527998225d4654bad4d3edb7380523849d28d","pi-packages\u002Fpi-skill-hepha-companion\u002Fskills\u002Fserialized-build-commands","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess","https:\u002F\u002Fgithub.com\u002Faboimpinto","2026-10-31 15:24:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill serialized-build-commands",{"tool":36,"command":37},"bunx","bunx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill serialized-build-commands",{"tool":39,"command":40},"pnpm","pnpm dlx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill serialized-build-commands","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-companion\u002Fskills\u002Fserialized-build-commands\u002FSKILL.md",true,[],[45,50,57,64,71,78],{"skillNo":46,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":47,"categories":48,"keywords":49,"publishedAt":19},"01M7C6RES661REA4K3SSD410VM","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-serialized-build-commands\u002Fskills\u002Fserialized-build-commands\u002FSKILL.md",[],[],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7C6R9EFN2C4620CFRMM5SMK","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\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fsubmit-epic\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7C6R5H2SW40BQ3GJ61SSFP4","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\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fstart-feature\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7C6R0NN4CAK6VPMPJH4Y5K3","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\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Frefine-feature\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7C6QWEKWY4AEFDCBCXKE9E8","design-feature","Use when the user asks Pi to run design-feature, design a HEPHA FEAT, create UI requirements, or prepare UX\u002Fdesign artifacts for a FEAT, for example \"design-feature FEAT-004\" or \"Use the design-feature skill for HEPHA FEAT-004\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fdesign-feature\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7C6QSJEJ7GZP51CGKNPN27D","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\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fdeep-dive\u002FSKILL.md",[],[]]