OpenSkillIndex← back to search
claude-code

Bernstein bernstein-approve

install
source · Clone the upstream repo
git clone https://github.com/chernistry/bernstein
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/chernistry/bernstein "$T" && mkdir -p ~/.claude/skills && cp -r "$T/packages/cursor-plugin/skills/bernstein-approve" ~/.claude/skills/chernistry-bernstein-bernstein-approve && rm -rf "$T"
manifest: packages/cursor-plugin/skills/bernstein-approve/SKILL.md
source content

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

  1. When the user decides:

    • Approve: 
      scripts/approvals.sh approve <task_id> "reason"
    • Reject: 
      scripts/approvals.sh reject <task_id> "reason"

  2. 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

  1. 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