/bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
$ npx -y skills add sipyourdrink-ltd/bernstein --skill bernstein-approve --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/bernstein-approve
Context preview
The summary Claude sees to decide when to auto-load this skill.
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
SKILL.md
bernstein-approve.SKILL.mdname: bernstein-approve
description: >
Review and approve/reject pending tasks or plans in Bernstein.
Use when the user asks about approvals, wants to review agent work,
or needs to approve/reject a plan before execution begins.
Bernstein Approvals
Review pending approvals and plans, then approve or reject them.
When to Use
- User asks "any pending approvals?" or "what needs my review?"
- User wants to approve or reject a completed task
- User wants to review and approve/reject a plan before agents execute it
- User says "approve that" or "reject task X"
Instructions
List pending approvals
1. Run `scripts/approvals.sh list` to fetch pending approvals and plans. 2. Present each item with its diff summary and test results:
## Pending Approvals
### Task TASK-042: Fix auth middleware
**Agent:** claude-backend-01 | **Role:** backend
**Files changed:** src/auth/middleware.py (+42 -8)
**Tests:** 14/14 passing
[Approve] [Reject]
Approve or reject
3. When the user decides:
- Approve: `scripts/approvals.sh approve <task_id> "reason"`
- Reject: `scripts/approvals.sh reject <task_id> "reason"`
4. For **plans** (multi-task proposals):
- List plans: `scripts/approvals.sh plans`
- Approve plan: `scripts/approvals.sh approve-plan <plan_id>`
- Reject plan: `scripts/approvals.sh reject-plan <plan_id>`
After approval
5. Confirm the action and note what happens next:
- Approved tasks → agent commits and merges
- Approved plans → planned tasks promoted to open, agents start picking them up
- Rejected → task goes back to open for retry, or gets cancelled
Read more
name: bernstein-approve description: > Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
Bernstein Approvals
Review pending approvals and plans, then approve or reject them.
When to Use
- User asks "any pending approvals?" or "what needs my review?"
- User wants to approve or reject a completed task
- User wants to review and approve/reject a plan before agents execute it
- User says "approve that" or "reject task X"
Instructions
List pending approvals
1. Run `scripts/approvals.sh list` to fetch pending approvals and plans. 2. Present each item with its diff summary and test results:
## Pending Approvals ### Task TASK-042: Fix auth middleware **Agent:** claude-backend-01 | **Role:** backend **Files changed:** src/auth/middleware.py (+42 -8) **Tests:** 14/14 passing [Approve] [Reject]
Approve or reject
3. When the user decides:
- Approve: `scripts/approvals.sh approve <task_id> "reason"`
- Reject: `scripts/approvals.sh reject <task_id> "reason"`
4. For **plans** (multi-task proposals):
- List plans: `scripts/approvals.sh plans`
- Approve plan: `scripts/approvals.sh approve-plan <plan_id>`
- Reject plan: `scripts/approvals.sh reject-plan <plan_id>`
After approval
5. Confirm the action and note what happens next:
- Approved tasks → agent commits and merges
- Approved plans → planned tasks promoted to open, agents start picking them up
- Rejected → task goes back to open for retry, or gets cancelled
Deterministic orchestrator for CLI coding agents (Claude Code, Codex, Gemini CLI, +40 more). No model in the coordination loop, so parallel runs in per-task git worktrees replay byte-identically. Signed lineage plus an opt-in HMAC audit chain a reviewer checks offline, without rerunning it. Cluster mode, air-gap deploy. https://bernstein.run
Repo: sipyourdrink-ltd/bernstein
Other skills on bernstein.
- /bernstein-agents
Manage Bernstein agents - list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.
Open skill - /bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
Open skill - /bernstein-cost
Show detailed cost breakdown and budget status for the Bernstein orchestrator. Use when the user asks about spending, budget, cost per model, cost per agent, or wants a cost projection.
Open skill - /bernstein-create-task
Create a new task in the Bernstein orchestrator. Use when the user wants to add a task, delegate work to an agent, file a bug fix, or queue up work for the orchestrator to handle.
Open skill - /bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
Open skill - /bernstein-quality
Show quality metrics for Bernstein runs - success rates per model, lint/test pass rates, completion time distributions. Use when the user asks about quality, reliability, which model performs best, or pass rates.
Open skill