← ClaudeAtlas

test-permission-long-editlisted

Trigger a permission prompt for a long Edit (large old_string and new_string), useful for testing how the Edit-tool permission UI renders big diffs.
brianwestphal/hotsheet · ★ 6 · Testing & QA · score 71
Install: claude install-skill brianwestphal/hotsheet
Trigger an Edit-tool permission prompt with a LONG diff. The earlier version of this skill seeded the fixture via a Bash heredoc (`cat > file <<EOF`), which surfaced as a **Bash run** permission prompt rather than an Edit prompt — defeating the skill's stated purpose (per HS-8300, the user reported "the current test-permission-long-edit skill doesn't actually do an 'edit', it runs a program that does an edit"). The current flow uses the Write tool to seed the fixture (which surfaces the Write permission UI) and then the Edit tool to perform the actual long-diff edit (which surfaces the Edit permission UI — this skill's true target). 1. Generate a fresh `<unique>` value (a Unix timestamp with nanoseconds, or a short random hex string) so the target path is brand-new each run. Do not reuse a value from a previous invocation. 2. Use the Write tool to create `/tmp/claude-permission-test/long-edit-<unique>.txt` with this exact 10-line block (substitute your fresh `<unique>` value into the path): ``` alpha line one — original alpha line two — original alpha line three — original alpha line four — original alpha line five — original alpha line six — original alpha line seven — original alpha line eight — original alpha line nine — original alpha line ten — original ``` Do NOT Read the file first — it doesn't exist yet, and reading it would defeat the "brand new file" prompt path the Write call is meant to surface. 3. Read the file once with t