yigitkonur

Auto Approve Claude Plan — Development skill for Claude Code

Development community

auto-approve Claude Code plans instantly — optional Craft.do archiving.

How to install Auto Approve Claude Plan

This entry records only its repository, not the path inside it, so there is no exact command to give. Open yigitkonur/hooks-claude-code and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Auto Approve Claude Plan does

auto-approve Claude Code plans instantly — optional Craft.do archiving.

Alternatives in Development

Implementation Plan — You are tasked with creating detailed implementation plans through an interactive, iterative process 10k ★
Dev Plan — /dev-plan — Génère les plans techniques d'1 FEAT sans coder 193 ★
YOLO/Auto-Mode 분류기 시스템 — 관찰 위치: Claude Code 내부 아키텍처 Tool 호출을 자동 승인할지 차단할지 결정하는 2단계 보안 분류 시스템입니다 149 ★

README

auto-approves Claude Code's "ready to code?" plan dialog so you stop clicking a button 50 times a day. an optional **Deep Plan** mode also nudges Claude to reason harder *while you're in plan mode* and gives you effort-tier launch aliases. pure bash, no dependencies beyond `jq`.

bash <(curl -fsSL https://raw.githubusercontent.com/yigitkonur/auto-approve-claude-plan/main/install.sh)

[![bash](https://img.shields.io/badge/bash-pure_shell-93450a.svg?style=flat-square)](https://www.gnu.org/software/bash/) [![platform](https://img.shields.io/badge/platform-macOS_|_Linux-93450a.svg?style=flat-square)](#) [![license](https://img.shields.io/badge/license-MIT-grey.svg?style=flat-square)](https://opensource.org/licenses/MIT)

the problem

Claude Code has a plan mode. when Claude finishes writing a plan and calls `ExitPlanMode`, it fires a `PermissionRequest` event and waits for you to click approve. every single time. this hooks into that event and returns `{"behavior":"allow"}` immediately — and also asks Claude Code to land the session in `bypassPermissions` so subsequent tool calls don't prompt either.

two modes

the installer asks you to pick one:

mode	what it does
1 — Classic (default bypass)	approves every plan instantly and lands the session in `bypassPermissions`. nothing else is touched. install and forget
2 — Deep Plan (recommended)	everything in Classic, plus a prompt-level boost: while you are in plan mode every prompt is nudged to reason deeply (auto-reverts when you leave plan mode), `effortLevel` is set to `low` as a cheap normal-mode baseline, and two launch aliases (`claude-plan` / `claude-fast`) are added to your shell

The old **Orchestrator** mode has been removed. Re-running the installer over an existing Orchestrator install cleans up its `PostToolUse` hook automatically.