fix(pstack): name a callable UI driver and a todolist tool on Claude Code

[michael-denyer]

Why

Claude Code's bundled /verify is user-invocable only, so an agent following the UI playbooks could not call the named driver. The todolist rule also named no concrete tool or fallback when task tools were unavailable.

What changes

Driver selection lives in poteto-mode Non-negotiables. Playbooks refer to that policy, and worker briefs carry the selected skill path or exact commands. The policy uses a project verify skill for UIs and falls back to run. The generator writes .claude/skills/verify/; maintenance still accepts older verify-* skills. The single control skill → driver skill substitution keeps platform selection out of the sync rules, and sync diagnostics point to the policy. The generator retains both control-skill and driver-skill discovery phrases.

The checklist uses available task-tracking tools or an uncommitted todo.md with verbatim playbook steps and skip reasons. The setup guidance links to the documented task-tool opt-in and describes model-dependent defaults. The version requirement for project skill replacement links to the official Claude Code documentation.

Issue-linked tests protect the driver policy, generator name, legacy maintenance lookup, and checklist fallback. New denylist entries let the existing installed-plugin sync test catch obsolete UI instructions. Tests also check the emitted repair advice and permit legitimate project and legacy skill references.

Version 0.9.29; upstream pin remains e8d856f.

Verification

• bun test: 244 passed, 0 failed.
• bun tools/generate.mjs: generated files current; layout and local links valid.
• Markdown lint: 152 files, 0 issues. git diff --check passes.
• Sync comparison against the local checkout of upstream e8d856f, using syncComponent with the CLI's derivation and exclusions: 57 forked, 66 unchanged, 35 excluded; no writes, conflicts, or denylist hits. The fork count is unchanged.
• Before the fixes, regression checks failed on orchestrate.md's obsolete UI instruction and the stale sync diagnostic; they pass after the fixes.
• Earlier isolated Claude Code 2.1.252 probes invoked the root verify and nested apps/web:verify skills successfully. Skill naming and placement are unchanged by this follow-up; the probes were not repeated.

Closes #71
Closes #72

[coldtea-pr-lens]

◈ PR Lens

🟢 +0 new · 🟠 ~8 changed · 🔴 -0 removed · 1 flow · 20 files · commit 160230b

Architecture

8 components touched across 5 lanes.

Open the interactive canvas

Inside the changed components — 2 views

Component view — Driver policy and verification

poteto-mode centralizes driver selection in Non-negotiables, redirecting playbooks to project .claude/skills/verify/ or fallback run.

Component view — Sync substitutions and rule tests

Sync substitution rules simplify control skill translation and test suites pin rules for issue #71 and #72.

Data flow

Resolving and running app verification

Open the interactive canvas

View

• Architecture lens
• Data flow lens
• Expand every detail

Tip

Open a diagram on the canvas, then press W or click play to walk through the change one step at a time.

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists.
• Untick Architecture lens or Data flow lens under View to hide a diagram, or tick Expand every detail to open every section. The comment redraws in a few seconds.
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through.
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change.
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time.
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs on every push.
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works.
• Push a commit and the comment redraws for the new head. A slow older run never overwrites a newer one.
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion.

---

Thanks for using PR Lens! It's built by Coldtea, free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn