ArcanEdge-AI
- 6 skills
- 0 followers
- 7 hours ago last updated
- ▌ Senior Code Review · arcanedge-aiUse before finalizing a meaningful code change. Reviews the final diff for correctness bugs, regressions, scope creep, missing tests, safety, performance, accessibility, and maintainability risk — and for subagent claims that were never independently verified.
- ▌ Worktree Lifecycle · arcanedge-aiUse when Git worktree isolation is being proposed for a Claude Code task, when parallel writers might need filesystem isolation, when a task already owns an auxiliary checkout, or when a task-created worktree must be integrated, preserved, or removed before finishing. Keeps worktree use finite, root-owned, and reconciled inside the task.
- ▌ Reference Doc Routing · arcanedge-aiUse when a task might need architecture, testing, access-control, design-system, API, release, data-model, subagent, or worktree reference documents. Helps pick the ones that matter, judge how much authority each has, read only the relevant sections, and pass concise labeled context to subagents.
- ▌ Subagent Orchestration · arcanedge-aiUse when planning how to delegate a coding task to Claude Code subagents — deciding whether to delegate at all, which role fits, how to write an assignment that comes back usable, how to run several safely in parallel, and how to verify results before accepting them. Use multi-session-coordination instead when other independent Claude Code sessions already own related work.
- ▌ Task Graph Orchestration · arcanedge-aiUse for a complex Claude Code task with substantial fan-out, several genuine dependencies, broad repository scope, layered consolidation, separate implementation and verification paths, or an approval-gated irreversible action. Makes the work topology explicit in Markdown, runs only the parts whose inputs are ready, preserves completeness through consolidation, and reruns only what a failure actually invalidated. Skip it for small or genuinely linear work.
- ▌ Multi Session Coordination · arcanedge-aiUse when several independent Claude Code sessions are working on related areas of the same project and someone has to hold the whole picture — discovering what is in flight, detecting incompatibilities beyond merge conflicts, assigning ownership of shared contracts, sequencing the work, and planning integration. Not for ordinary subagent delegation within one session.