메뉴
Hand off a bounded implementation or review pass to Claude through ACPX.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Fork one isolated Codex worktree thread per Beads issue and start each with a dependency-aware completion contract. Use when the user asks to start, fork, split, parallelize, or create separate chats for beads, tickets, issues, or a backlog with the goal of fixing them all.
This skill should be used when the user asks to "bump a package", "update an upstream revision", "refresh a Nix source hash", "rebase local patches", "carry fork changes as patches", "hack on upstream software in this repo", or fix a package whose patches no longer apply.
Jujutsu version control through jut, a human and agentic framework around jj. Use for: check status, view changes, commit work, create branches, push, pull, create PRs, squash commits, reword messages, absorb changes, undo operations, view history. Complements jj — use jut for opinionated workflows, drop into raw jj for everything else.
Create, manage, and verify healthchecks.io monitors via the REST API. Use when adding monitoring to a new cron job or service, auditing existing checks, wiring ping URLs into configs, or verifying a check fired correctly.
Control live Herdr workspaces, tabs, panes, agents, worktrees, layouts, plugins, and waits. Use when running inside Herdr (`HERDR_ENV=1`) to inspect sibling agents, delegate work—including dedicated Pi workspaces—run services, debug agent detection, or coordinate terminal state.
Structural code search, refactoring, and repository lint-rule setup with ast-grep. Use when searching by syntax shape, writing or testing ast-grep rules, configuring sgconfig.yml, enforcing coding standards, selecting rule severity, or adding ast-grep to project checks and CI.
| name | acpx-claude |
| description | Hand off a bounded implementation or review pass to Claude through ACPX. |
Use this skill when the user asks to run acpx claude, wants a Claude ACP agent, or when a task would benefit from a second-agent implementation/review pass through Claude Code.
One-shot prompt without a saved session:
acpx claude exec "review the recent changes and identify risks"
Persistent session for the current repo:
acpx claude "investigate this bug and propose a fix"
acpx claude prompt "continue with the smallest safe patch"
acpx claude status
Named session:
acpx claude -s backend "debug the failing API tests"
acpx claude -s backend prompt "apply the fix and summarize the diff"
acpx claude is allowed by the local Pi permission policy for this dotfiles setup.hey, signing hooks, rebuild/deploy rails, or destructive Nix cleanup.exec vs persistent promptsUse exec for independent checks, summaries, or reviews where no session continuity is needed.
Use the persistent acpx claude / prompt flow for multi-step implementation where Claude should keep context between turns.
We are in /Users/emiller/.config/dotfiles. Goal: <specific outcome>.
Constraints: preserve existing Nix/hey safety rails; do not run direct rebuild/deploy commands.
Please inspect <files/commands>, make the minimal patch if appropriate, then summarize changes and validation.