About claude-code
A Claude Code operating skill for running coding tasks with explicit controls for permissions, sessions, worktrees, output, and verification. It is intended for workflows that need a recorded command and evidence-based outcome reporting.
Key features
- 01Configurable permission and run modes
- 02Session and worktree handling
- 03Output format selection
- 04Diff and test verification
Use cases
- 01Run a coding task in a chosen workspace
- 02Resume or continue a Claude Code session
- 03Review changes from a worktree
- 04Verify edits before reporting results
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ prathamdby/ skills --skill claude-codeAfter installing, type/claude-codein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/install.mdmanagement.mdpermissions.mdsessions.mdstreaming.mdworktrees.mdDetails
From the project READMEClaude Code
Options and boundaries
Default: claude --print --dangerously-skip-permissions --output-format text "<prompt>"
from the target directory; model omitted; parent wait 15m. Calling this skill
authorizes that run: pass --dangerously-skip-permissions without asking.
There is no --yolo flag; this skip is the yolo run. Print alone can write.
"Read-only" / "plan" uses --permission-mode plan and omits the skip flag.
"Use " adds --model. "Interactive" / "TUI" omits --print and the
skip flag. "Resume " adds --resume; "continue" adds --continue; both wait
until exit and keep the same permission choice as the selected mode.
"Worktree [name]" adds --worktree [name]; record the emitted path.
"JSON" / "stream-json" selects that print output. Missing needed values or
conflicting options are BLOCKED.
For plan, restricted, or another named permission mode, follow
references/permissions.md. A default run does not stop for a permission
prompt. claude help starts a session: use claude --help.
remote-control is not documentation.
1. Resolve
Fix absolute workspace, prompt, mode, session, worktree, output, and wait.
Check binary and claude auth status --text without exposing secrets.
Missing binary → follow references/install.md; missing auth → BLOCKED
unless login was requested. Wrong cwd blocks.
Record cmd | workspace | mode | session | worktree | wait | evidence | terminal.
Done when target, binary, auth, and the permission choice are fixed.
2. Run
Build argv from those options and quote the prompt literally. Default text
is quiet until process exit; silence is not a hang. Wait for exit or the
recorded deadline, and kill only this run's PID when that deadline expires.
Nonzero exit: capture stderr, inspect the tree, and report BLOCKED.
Do not ask the user and do not add a second bypass.
For JSON/stream output, follow references/streaming.md. For resume,
continue, or background sessions, follow references/sessions.md.
For worktrees or parallel runs, follow references/worktrees.md.
For an asked-for TUI or management command, follow references/management.md.
A rejected flag requires scoped --help, not a guessed replacement.
Done when the process exits, an intended live handle is recorded, or a
failure is reported.
3. Verify and report
Inspect status and diff; CLI text is not proof. Run the narrowest covering tests for edited executable code. Plan mode must leave the tree unchanged. Verify each worktree and any integrated tree. Clean up only this run's sessions/worktrees unless explicitly kept; preserve auth, MCP, and plugins. Report command, mode, session/worktree, wait, and outcome evidence. Done when every requested outcome is observed or a blocker is evidenced.
Terminals: SUCCESS, NO_CHANGES, BLOCKED.