From 56e96e09ac94cabbb80d59b8424f4e17f25099f8 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Tue, 17 Nov 2026 01:36:12 +0000 Subject: [PATCH] Fix port audit issues 57-60 Point autopilot's decision trail and subagent record at work-dir files, drop the extra live-lane worktree, and name Devin's .agents skill paths plus the Windows global write dest. Point README skill authoring at the authoring playbook. Co-authored-by: Kaitian Xie --- README.md | 2 +- skills/automate-me/SKILL.md | 4 ++-- skills/maintain-verification-skill/SKILL.md | 2 +- skills/poteto-mode/playbooks/autopilot-full.md | 2 +- skills/poteto-mode/playbooks/multi-phase-plan.md | 2 +- skills/reflect/SKILL.md | 2 +- skills/reflect/references/divergent-reviewer.md | 2 +- skills/reflect/references/judgment-reviewer.md | 2 +- skills/reflect/references/tooling-reviewer.md | 2 +- 9 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index b3650c4..7b25513 100644 --- a/README.md +++ b/README.md @@ -250,7 +250,7 @@ twenty-four short skills, one principle each. `poteto-mode` indexes them inline a few things `poteto-mode` references but doesn't bundle: -- `/create-skill` is a cursor built-in. cursor also ships a built-in `/autopilot` that watches a pr. inside `poteto-mode`, pr-status requests go to the [babysit playbook](./skills/poteto-mode/playbooks/babysit.md) instead. +- author a skill with the [Authoring or modifying a skill playbook](./skills/poteto-mode/playbooks/authoring-a-skill.md). inside `poteto-mode`, pr-status requests go to the [babysit playbook](./skills/poteto-mode/playbooks/babysit.md) instead. ## why are there no planning skills? diff --git a/skills/automate-me/SKILL.md b/skills/automate-me/SKILL.md index 353b6ce..4e2fbaa 100644 --- a/skills/automate-me/SKILL.md +++ b/skills/automate-me/SKILL.md @@ -14,7 +14,7 @@ This skill orchestrates three passes: an inline mining pass (see step 1), SKILL. ### 0. Check for an existing skill -Look recursively for `.devin/skills/**/*-mode/SKILL.md` and `~/.config/devin/skills/*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.devin/skills//`), not only at the top level. If one exists, confirm intent with `ask_user_question` (unless they already said "update my skill" or similar): +Look recursively for `.devin/skills/**/*-mode/SKILL.md`, `.agents/skills/**/*-mode/SKILL.md`, `~/.config/devin/skills/*-mode/SKILL.md`, and `~/.agents/skills/*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.devin/skills//` or `.agents/skills//`), not only at the top level. If one exists, confirm intent with `ask_user_question` (unless they already said "update my skill" or similar): - Update the existing skill (default for repeat runs) - Start fresh (rare, ask why before doing it) @@ -66,7 +66,7 @@ The **poteto-mode** skill shows the shape. Read it for granularity. Don't copy i Author the SKILL.md directly, following Devin's skill format (YAML frontmatter over a prompt body). Placement: -- Path: preserve an existing mode skill's category. For a new mode, use `.devin/skills//-mode/SKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.devin/skills/-mode/SKILL.md` in the project (or `~/.config/devin/skills/-mode/` if the user prefers a personal skill). +- Path: preserve an existing mode skill's category, including one under `.devin/skills/`, `.agents/skills/`, `~/.config/devin/skills/`, or `~/.agents/skills/`. For a new mode, use `.devin/skills//-mode/SKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.devin/skills/-mode/SKILL.md` in the project (or `~/.config/devin/skills/-mode/`, `%APPDATA%\devin\skills\-mode\` on Windows, if the user prefers a personal skill). - Handle: the user's first name or chosen identifier. - Frontmatter `description`: trigger on their name + `/-mode` + "work in their style", not on generic keywords like "write code" or "review PR". - Frontmatter formatting: keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it. diff --git a/skills/maintain-verification-skill/SKILL.md b/skills/maintain-verification-skill/SKILL.md index f737044..53b1659 100644 --- a/skills/maintain-verification-skill/SKILL.md +++ b/skills/maintain-verification-skill/SKILL.md @@ -22,7 +22,7 @@ Only edit the verification skill's own directory (its SKILL.md, features/, and a ## Pass -0. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map (usually `.devin/skills/verify-*/`). Several candidates → ask which one; none → stop and point at `/pstack:create-verification-skill` instead of inventing a target. +0. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map (usually `.devin/skills/verify-*/` or `.agents/skills/verify-*/`). Several candidates → ask which one; none → stop and point at `/pstack:create-verification-skill` instead of inventing a target. 1. **Index hygiene.** Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory. diff --git a/skills/poteto-mode/playbooks/autopilot-full.md b/skills/poteto-mode/playbooks/autopilot-full.md index e1d12dd..8bf038c 100644 --- a/skills/poteto-mode/playbooks/autopilot-full.md +++ b/skills/poteto-mode/playbooks/autopilot-full.md @@ -9,7 +9,7 @@ A verdict covers one patch and green CI covers one head. Step 4 runs a full swar Open the PR early so CI and bots run alongside the work. The code is ready only after the slop-strip (the `deslop` skill (`/deslop`)) and the `/pstack:no-comments` pass, so the full swarm runs on finished code. Then rebase onto current trunk and report the code-ready head before self-proof, so verification runs on the base the patch lands on. Report every later head, and merge-ready once self-proof, CI, and babysit are done. Fix rounds stay on that base unless trunk conflicts, breaks CI, or lands a known concurrent change to the same files, because each rebase restarts CI. Run the repo's checks for the touched paths on the committed head before the code-ready push and before a later push that needs a verifier. - Assume the VM dies. Soon after starting, push and start a decision trail in the root agent's store (path in the system prompt) per the **show-me-your-work** skill, then push each finished unit before you start the next. Whoever spawns a subagent records its id, state, and a stuck-after runtime from past runs of its kind in that store, so the root can probe it if the parent dies. Force-push only your own branch, with `--force-with-lease` pinned to the SHA you last pushed or took over, and on any push you did not make, stop and report to the root. + Assume the VM dies. Soon after starting, push and start a decision trail at `decisions.tsv` in the work dir, or `.audit/.tsv` when several efforts run at once, per the **show-me-your-work** skill, then push each finished unit before you start the next. Whoever spawns a subagent records its id, state, and a stuck-after runtime from past runs of its kind in an adjacent file in the same directory. Push both with the branch, because the VM dies, so the root can probe it if the parent dies. Force-push only your own branch, with `--force-with-lease` pinned to the SHA you last pushed or took over, and on any push you did not make, stop and report to the root. 3. **Run owners in parallel off trunk, never stacked,** so each PR lands on its own. 4. **Swarm-verify once.** A full swarm runs once, at the code-ready head. Another full swarm runs only for new behavior, a redesign, or a large new diff. A rebase, a merge-conflict resolution, or a minor fix gets a single verifier at the new head, and a wording-only change gets none. Fan out independent verifiers at the code-ready SHA per the **swarm** skill. They re-run the gates, prove the load-bearing behavior live on the real surface through its control skill (such as `control-ui` or `control-cli`) or a named driver, and audit the diff. The verdict is not clean without the live lane, or before you audit the merge-ready report's receipts, because no lane trusts a claim it has not checked. diff --git a/skills/poteto-mode/playbooks/multi-phase-plan.md b/skills/poteto-mode/playbooks/multi-phase-plan.md index 8e509fc..2d4a53d 100644 --- a/skills/poteto-mode/playbooks/multi-phase-plan.md +++ b/skills/poteto-mode/playbooks/multi-phase-plan.md @@ -68,7 +68,7 @@ Tests alone are not sufficient verification. A PR is verified only when its unit ### Boot recipe, for every live lane -Each live lane runs on its own cloud VM (a `devin --cloud -p` session) or worktree at the PR head. Drive through `control-ui` or `control-cli`. +Each live lane runs on its own cloud VM (a `devin --cloud -p` session) at the PR head. Drive through `control-ui` or `control-cli`. - [ ] `git fetch origin && git checkout `. - [ ] diff --git a/skills/reflect/SKILL.md b/skills/reflect/SKILL.md index 8e7bb23..eb6829b 100644 --- a/skills/reflect/SKILL.md +++ b/skills/reflect/SKILL.md @@ -48,7 +48,7 @@ Present the synthesizer's full Accepted / Rejected / Backlog output and wait for File each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval. -Never edit a skill under `plugins/cache/`. Before approval, show its destination, `.devin/skills//` or `~/.config/devin/skills//`. After approval, copy the skill folder there and edit the copy. Never open a PR or push. +Never edit a skill under `plugins/cache/`. Before approval, show its destination: keep a skill already under `.devin/skills/`, `.agents/skills/`, `~/.config/devin/skills/`, or `~/.agents/skills/` where it is; otherwise `.devin/skills//` or `~/.config/devin/skills//` (`%APPDATA%\devin\skills\\` on Windows). After approval, copy the skill folder there and edit the copy. Never open a PR or push. Follow each approved row's Routing exactly: diff --git a/skills/reflect/references/divergent-reviewer.md b/skills/reflect/references/divergent-reviewer.md index a14a80d..7347aff 100644 --- a/skills/reflect/references/divergent-reviewer.md +++ b/skills/reflect/references/divergent-reviewer.md @@ -18,7 +18,7 @@ Scan for: ## Scope to skills and tools the session actually used -Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `~/.config/devin/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. +Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `.agents/skills/`, `~/.config/devin/skills/`, `~/.agents/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. Two finding shapes are valid: - The parent invoked the skill and you found a real gap in its body. Route to the skill's relevant section. diff --git a/skills/reflect/references/judgment-reviewer.md b/skills/reflect/references/judgment-reviewer.md index 1362443..8186ced 100644 --- a/skills/reflect/references/judgment-reviewer.md +++ b/skills/reflect/references/judgment-reviewer.md @@ -17,7 +17,7 @@ Scan for: ## Scope to skills and tools the session actually used -Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `~/.config/devin/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. +Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `.agents/skills/`, `~/.config/devin/skills/`, `~/.agents/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. Two finding shapes are valid: - The parent invoked the skill and you found a real gap in its body. Route to the skill's relevant section. diff --git a/skills/reflect/references/tooling-reviewer.md b/skills/reflect/references/tooling-reviewer.md index d6ccd1e..400f2ae 100644 --- a/skills/reflect/references/tooling-reviewer.md +++ b/skills/reflect/references/tooling-reviewer.md @@ -28,7 +28,7 @@ Scan for: ## Scope to skills and tools the session actually used -Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `~/.config/devin/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. +Route findings only to skills, tools, or MCPs this transcript used. A skill counts as used when the transcript shows a `read` of its `SKILL.md` (under `.devin/skills/`, `.agents/skills/`, `~/.config/devin/skills/`, `~/.agents/skills/`, or an installed plugin's `skills/`), a `run_subagent` prompt naming its path, or a tool call (exec, grep, MCP, etc.) matching its documented commands. Speculative routings to skills the parent never opened do not count. Two finding shapes are valid: - The parent invoked the skill and you found a real gap in its body. Route to the skill's relevant section.