Skip to content

Warn about install permission prompts, from a real walkthrough run - #29

Merged
ovhirup merged 1 commit into
mainfrom
claude/measured-reports-gate-iteration-i2wr67
Oct 31, 2026
Merged

ovhirup merged 1 commit into
mainfrom
claude/measured-reports-gate-iteration-i2wr67

Conversation

@ovhirup

@ovhirup ovhirup commented Oct 31, 2026

Copy link
Copy Markdown
Owner

Fixes #11: the last criterion, a run of the walkthrough in a real Claude Code session.

What was run

docs/first-task.md was run end to end in Claude Code 2.1.316, in a throwaway home directory and project, against the published 3.4.0 plugin:

Step Result
1. claude plugin marketplace add ovhirup/stackwich + install stackwich@stackwich ✓ installed 3.4.0 from GitHub
1. Run /stackwich:stackwich ✗ blocked by Claude Code's permission layer (see below); the skill changed nothing and reported every step 4 check as FAIL
1. Diagnostics + check_install.py (scope written with exactly what the installer writes) ✓ INSTALL: PASS, policy-rev 7, three Stackwich agents
3. Demo fails ✓ FAILED (failures=1)
4. The walkthrough's prompt ✓ one-line fix to total(); the verifier subagent re-ran the tests, checked scope, and returned GATE: PASS; the report quoted the command and counted 1 subagent. Independent check: tests pass, test_cart.py unchanged
6. uninstall.py then claude plugin uninstall / marketplace remove ✓ removed the Stackwich block and agents, kept the user's own notes and agent, wrote a backup; the plugin and marketplace were removed

The gap found

Claude Code protects CLAUDE.md and files outside the project. In non-bypass modes, the skill needs permission to write CLAUDE.md, read the plugin's agent files, and create agents/. If any of those is refused, the install does not happen. The skill handled this well: it did not work around the block, it reported each check as FAIL, and it said what to allow. But neither the README nor the walkthrough warned users to expect these prompts.

Change

  • README Install and docs/first-task.md step 1 now say to expect and approve those prompts, and what happens if one is refused.
  • docs/first-task.md notes the recorded run and summarises what the step 4 session did.

Verification

  • All skill-lint steps pass locally.
  • The run's transcript was checked for the verifier's own GATE: PASS and scope check, not just the final message.

Generated by Claude Code

docs/first-task.md was run end to end in Claude Code 2.1.316 against
the published 3.4.0 plugin. Installing from GitHub, the gated fix with
the verifier subagent, and the uninstall all behaved as documented. The
one gap: Claude Code asks permission before the skill writes CLAUDE.md,
reads the plugin's agent files, and creates agents/, and a refused write
leaves the install undone. README and the walkthrough now say so, and
the walkthrough summarises what the recorded step 4 session did.

Fixes #11

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TgCNfzRULZvxaP1GfyqzRe
@ovhirup
ovhirup marked this pull request as ready for review October 31, 2026 07:38
@ovhirup
ovhirup merged commit 4788560 into main Oct 31, 2026
2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-31T07:39:18.576331Z b6059fd Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a guided first verified task and installation diagnostics

2 participants