بنقرة واحدة
patchmill-development-environment
Use when Patchmill dogfoods its own development stage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when Patchmill dogfoods its own development stage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when executing Patchmill implementation plans that require one plan implementation subagent and final full-worktree readiness review before landing
Use when executing Patchmill implementation plans that require final full-worktree readiness review before landing
Use when executing Patchmill implementation plans with Superpowers task-level development plus final validation and pull-request readiness, without extra Codex or thermo-nuclear full-worktree reviews
Decide when Patchmill may direct-land and when it must open a PR.
Use when Patchmill run-once changes visible UI and needs committed reference screenshot evidence in the final pr-created JSON.
Use for Patchmill run-once spec and plan creation. Wraps sibling Superpowers brainstorming and writing-plans skills with Patchmill worktree, artifact path, and test-value policy.
| name | patchmill-development-environment |
| description | Use when Patchmill dogfoods its own development stage. |
Prepare a Patchmill issue worktree so implementation can use the repository's
devenv + npm toolchain. This stage verifies local runtime readiness only; it
is not product implementation, review, or final validation.
patchmill run-once or
patchmill triage recursively.git status as a readiness gate. Patchmill owns clean-worktree
checks before this stage; unrelated tracked changes are not environment
failures unless they directly break the commands below.npm test, npm run build, or devenv tasks run patchmill:smoke
as default readiness gates. Those are implementation/final validation checks
and may legitimately fail before an issue is fixed.Run commands from the issue worktree root.
Confirm this is the Patchmill repository by checking for package.json,
package-lock.json, devenv.nix, and devenv.yaml.
Ensure dependencies exist. If node_modules/.package-lock.json is missing or
package-lock.json is newer than it, run:
devenv shell -- npm ci
Otherwise record that existing node_modules is being reused.
Verify the runtime:
devenv shell -- node --version
devenv shell -- npm --version
Node must be v24.x.
Run the cheapest Patchmill CLI smoke check:
devenv shell -- npm run patchmill -- version
Return strict final JSON only.
{
"status": "ready",
"summary": "Patchmill devenv and npm toolchain are ready",
"evidence": [
"devenv shell -- node --version -> v24.x",
"devenv shell -- npm --version -> <version>",
"devenv shell -- npm run patchmill -- version -> <version>"
],
"environment": {
"nodeVersion": "v24.x",
"npmVersion": "<version>",
"patchmillVersion": "<version>",
"dependencyState": "npm ci run or existing node_modules reused"
}
}
Return not-ready for local/operator environment failures such as missing
devenv, npm ci failure, wrong Node major version, or the Patchmill version
smoke check failing before implementation starts.
{
"status": "not-ready",
"reason": "short operator-facing reason",
"evidence": ["failed command and concise output summary"],
"remediation": [
"Run devenv shell -- npm ci from the issue worktree",
"Confirm devenv shell -- npm run patchmill -- version succeeds",
"Re-run patchmill run-once"
]
}