skills/press1-check/SKILL.md
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
npx skillsauth add arndvs/ctrlshft press1-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Output "Read Press1 Check skill." to chat to acknowledge you read this file.
Audit which Bash commands triggered manual approval prompts in Claude Code sessions.
Two paths:
/press1-check to force a re-audit. Default mode is since the last run (state-tracked at ~/.claude/state/press1-check.json), so the typical run only surfaces new ground.--auto-stop-hook mode designed to be wired as a Claude Code Stop hook. 6-hour cooldown. When LOW-risk additions are found, a one-shot summary surfaces in the next session-start priority snapshot.# Since the last run (default, state-tracked)
python3 skills/press1-check/audit-permissions.py
# Last N days across all project dirs
python3 skills/press1-check/audit-permissions.py --days 7
# Only the single most recent session
python3 skills/press1-check/audit-permissions.py --latest-session
# All sessions from the last 24h
python3 skills/press1-check/audit-permissions.py --all-recent
# All sessions since a date
python3 skills/press1-check/audit-permissions.py --since 2026-04-10
# Specific session (prefix match OK)
python3 skills/press1-check/audit-permissions.py <session-id>
/press1-check)python3 <skill-path>/audit-permissions.py with any arguments the user provided. Default audits since ~/.claude/state/press1-check.json#last_run_ts (bootstraps to last 3 days when state is missing).~/.claude/settings.json (read-only commands are safe). Skip env-var-prefix suggestions like Bash(WT=*) — they don't generalize.~/.claude/settings.json, re-run the audit and report before/after counts so the user sees the coverage delta.| Risk | Color | Policy | Example |
|------|-------|--------|---------|
| HIGH | Red | Keep gated — destructive or hard to reverse | rm, sudo, git reset --hard, DROP TABLE |
| MEDIUM | Yellow | Review case-by-case — side effects outside local repo | gh pr create, curl, docker, pip install |
| LOW | Green | Safe to allow-list — read-only or local-only | cat, ls, grep, wc |
*/subagents/*.jsonl and tags findingsdevelopment
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
tools
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
testing
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
testing
Pre-flight checklist that runs quality gates before ending a coding session.