press1-check

Audits Claude Code session logs to identify Bash commands that required manual approval.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill press1-check-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: press1-check
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/press1-check
Command: npx skills add https://github.com/arndvs/ctrlshft --skill press1-check-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code sessions accumulate manual "press 1 to approve" prompts for Bash commands not covered by the allow-list, interrupting flow and hiding which permissions should be added. This Skill audits session transcripts to surface exactly which commands triggered approvals and classifies them by risk. ## Core Features & Use Cases - Permission Auditing: Scans session JSONL files across all project directories under ~/.claude/projects/ to find Bash commands not covered by the settings.json allow-list. - Risk Classification: Labels each command HIGH (destructive), MEDIUM (external side effects), or LOW (read-only/local) and suggests allow rules sorted by risk. - Incremental State Tracking: Default runs audit only since the last run via ~/.claude/state/press1-check.json, with an optional Stop-hook mode featuring a 6-hour cooldown. - Use Case: After a week of sessions with frequent approval prompts, run the audit to get a color-coded list of suggested allow-list additions, then safely add the LOW-risk read-only commands to ~/.claude/settings.json. ## Quick Start Ask the assistant to run a permission audit with /press1-check to list which Bash commands required approval since the last run and suggest safe allow-list additions.

Frequently Asked Questions about press1-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit which Bash commands required approval in Claude Code?▼

Run the audit-permissions.py script with no arguments to scan all session logs since the last run. It prints each uncovered Bash command with a color-coded risk level and suggests allow-list rules for settings.json.

How do I reduce press 1 approval prompts in Claude Code sessions?▼

Run a permission audit to find LOW-risk commands like cat, ls, or grep that triggered prompts, then add the suggested Bash(prefix:*) rules to ~/.claude/settings.json. Re-run the audit to confirm the coverage delta.

Can the permission audit run automatically as a Stop hook?▼

Yes, the --auto-stop-hook mode is designed for the Claude Code Stop hook chain. It enforces a 6-hour cooldown, stays silent when nothing is actionable, and writes a pending summary when LOW-risk additions are found.

Does the audit script modify settings.json automatically?▼

No, the script never auto-applies changes. It only surfaces findings and proposes allow rules; MEDIUM and HIGH risk commands require explicit user approval before being added to the allow-list.

Why does the audit show commands from subagent sessions?▼

The script detects JSONL files under subagents directories and tags those findings with a subagent marker. This ensures commands run by spawned subagents are included in the permission coverage analysis.