diff --git a/harness/pstack/claude-code/docs/guide/05-build-and-clean.md b/harness/pstack/claude-code/docs/guide/05-build-and-clean.md index dbadc3d41..c4258986a 100644 --- a/harness/pstack/claude-code/docs/guide/05-build-and-clean.md +++ b/harness/pstack/claude-code/docs/guide/05-build-and-clean.md @@ -56,7 +56,7 @@ In context, that's enough. [`/tdd`](../../skills/tdd/SKILL.md) writes the smalle ## Clean before you commit -The [Opening a PR playbook](../../skills/poteto-mode/playbooks/opening-a-pr.md) runs `/deslop` on the diff before each commit and applies [`/unslop`](../../skills/unslop/SKILL.md) to the PR description and commit bodies. `/deslop` ships in the `cursor-team-kit` plugin, not in pstack. If you don't have it, ask for the same outcome in plain words: remove narrating comments, unsupported guards, dead compatibility paths, and unrelated edits. +The [Opening a PR playbook](../../skills/poteto-mode/playbooks/opening-a-pr.md) runs `/deslop` on the diff before each commit and applies [`/unslop`](../../skills/unslop/SKILL.md) to the PR description and commit bodies. `/deslop` ships in the `cursor-team-kit` plugin, not in pstack. If you don't have it, poteto-mode makes the same pass by hand. Outside poteto-mode, ask for it in plain words: remove narrating comments, unsupported guards, dead compatibility paths, and unrelated edits. For prose, `/unslop` takes a target and any extra rules you have: diff --git a/harness/pstack/claude-code/skills/poteto-mode/SKILL.md b/harness/pstack/claude-code/skills/poteto-mode/SKILL.md index 1bb3884a5..ce9b16139 100644 --- a/harness/pstack/claude-code/skills/poteto-mode/SKILL.md +++ b/harness/pstack/claude-code/skills/poteto-mode/SKILL.md @@ -27,7 +27,7 @@ Remaining triggers: - Nontrivial multi-step → write the throughput checkpoint (Feature step 3). - Any prose surface, your reply to the user included → the **unslop** skill. Write the reply per **Writing the reply**. Agent-facing prose also follows the **create-skill** skill (Cursor's built-in for authoring SKILL.md files). - Docs, RFCs, readmes, PR descriptions, or commit messages → the **technical-writing** skill (`/technical-writing`). -- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`). +- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`). Without that plugin, make the same pass yourself over the branch's diff and keep behavior unchanged. Cut comments the local style wouldn't have, defensive checks and try/catch that trusted code paths don't need, casts that only bypass the type checker, nesting that early returns flatten, and anything else unlike the surrounding code. - Before review → the **no-comments** skill (`/no-comments`). - Shipping UI / IDE / CLI → the matching control skill. `cursor-team-kit` publishes `control-cli` (CLIs and TUIs) and `control-ui` (browser / Electron / web UIs). For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception. - Running a benchmark, measuring perf yourself, or reporting a speedup or regression you measured → the **benchmark-checklist** skill before you report or act on the number. diff --git a/pstack/docs/guide/05-build-and-clean.md b/pstack/docs/guide/05-build-and-clean.md index dbadc3d41..c4258986a 100644 --- a/pstack/docs/guide/05-build-and-clean.md +++ b/pstack/docs/guide/05-build-and-clean.md @@ -56,7 +56,7 @@ In context, that's enough. [`/tdd`](../../skills/tdd/SKILL.md) writes the smalle ## Clean before you commit -The [Opening a PR playbook](../../skills/poteto-mode/playbooks/opening-a-pr.md) runs `/deslop` on the diff before each commit and applies [`/unslop`](../../skills/unslop/SKILL.md) to the PR description and commit bodies. `/deslop` ships in the `cursor-team-kit` plugin, not in pstack. If you don't have it, ask for the same outcome in plain words: remove narrating comments, unsupported guards, dead compatibility paths, and unrelated edits. +The [Opening a PR playbook](../../skills/poteto-mode/playbooks/opening-a-pr.md) runs `/deslop` on the diff before each commit and applies [`/unslop`](../../skills/unslop/SKILL.md) to the PR description and commit bodies. `/deslop` ships in the `cursor-team-kit` plugin, not in pstack. If you don't have it, poteto-mode makes the same pass by hand. Outside poteto-mode, ask for it in plain words: remove narrating comments, unsupported guards, dead compatibility paths, and unrelated edits. For prose, `/unslop` takes a target and any extra rules you have: diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.md index 21993f546..a9b616376 100644 --- a/pstack/skills/poteto-mode/SKILL.md +++ b/pstack/skills/poteto-mode/SKILL.md @@ -25,7 +25,7 @@ Remaining triggers: - Nontrivial multi-step → write the throughput checkpoint (Feature step 3). - Any prose surface, your reply to the user included → the **unslop** skill. Write the reply per **Writing the reply**. Agent-facing prose also follows the **create-skill** skill (Cursor's built-in for authoring SKILL.md files). - Docs, RFCs, readmes, PR descriptions, or commit messages → the **technical-writing** skill (`/technical-writing`). -- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`). +- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`). Without that plugin, make the same pass yourself over the branch's diff and keep behavior unchanged. Cut comments the local style wouldn't have, defensive checks and try/catch that trusted code paths don't need, casts that only bypass the type checker, nesting that early returns flatten, and anything else unlike the surrounding code. - Before review → the **no-comments** skill (`/no-comments`). - Shipping UI / IDE / CLI → the matching control skill. `cursor-team-kit` publishes `control-cli` (CLIs and TUIs) and `control-ui` (browser / Electron / web UIs). For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception. - Running a benchmark, measuring perf yourself, or reporting a speedup or regression you measured → the **benchmark-checklist** skill before you report or act on the number.