Claude Code Auto-Approval Quick Tips (90-Second Playbook)¶

ℹ️ Search insight (MCP Google Search Console, 2025-11-02–11-08)
Query Clicks Impressions CTR Position
claude code auto approval 8 14 57.1% 1.0
High CTR + low impressions means we need fresh tips + internal links to capture the demand.

1. Shift+Tab = instant mode verification¶

3 checks before running

Watch the mode pill on the top-right (Normal → Auto → Plan).
Auto mode is for safe fixes only—never run destructive commands there.
Tap Shift+Tab (or Esc) to leave Plan/Auto as soon as you finish the intended change.

Pro move: Run /status at the first turn and paste the mode/sandbox state into your TodoWrite log for auditability.

2. Pair every CLI flag with a stated scope¶

# Auto-approve only lint + test fixes
claude --dangerously-skip-permissions "Run eslint --fix && pnpm test"

# Auto-approve documentation rebuilds
claude --dangerously-skip-permissions "Build Storybook and refresh docs"

Declare in Slack/Issues which tasks are allowed to use the flag.
Any job that touches secrets or production infra must drop back to manual approvals.
Append && ./cleanup.sh so the same run also cleans artifacts.

3. Lock in observability with TodoWrite + transcripts¶

Step	Command	Why
Create task	`gh issue create --title "Claude auto approve" --project @me/4`	Spawn TodoWrite log + GitHub Project card
Capture transcript	`claude --dangerously-skip-permissions --transcript logs/claude_session.jsonl`	Persistent evidence in a logs directory
Sync parent issue	`gh issue comment <ISSUE#> --body "Progress: step N completed"`	Keeps project checklists green

Suggested attachment block

- Mode screenshot: [link]
- Transcript: logs/claude_session.jsonl
- Exception commands: (list anything risky)

Next actions¶

Duplicate your TodoWrite template, link these guides, and share the single source of truth with your team.