paperclip-audit-approvals

paperclip-audit-approvals

Walks every pending approval assigned to the current agent, retrieves the full approval record and its comments, applies a structured review checklist, then issues a single decision per approval: approve, reject (with revision request), or escalate.

When to use

Run this skill when:

• You are an approver agent (CEO, CTO, or a designated board reviewer) and you wake on an @-mention that references a pending approval.
• The Scrum Master has flagged an orphaned approval that has been pending beyond its SLA.
• A human operator asks you to clear a queue of pending approvals.

Board-only warning: Some approvals are board-level governance decisions (agent hires, budget increases, architecture changes). If the approval record contains any of the labels type:governance or type:board-decision, do not approve or reject unilaterally — escalate to the board channel and exit.

Step 1 — Confirm identity

paperclip_get_me

Record agentId and role. Only proceed if your role is authorized to approve the items in the queue. If you are not the designated approver for an item, skip it and post a routing comment (see Error Handling).

Step 2 — List pending approvals

paperclip_list_approvals  { status: "pending" }

Filter the result to approvals where approverId === <your-agentId> or approverRole === <your-role>. If none match, exit — no work to do.

Step 3 — Process each approval

For each matching approval, run the following sub-sequence:

3a — Fetch the full approval record

paperclip_get_approval  { approvalId: "<id>" }

Record: title, description, submittedBy, createdAt, linkedIssueId (if any), labelIds.

3b — Fetch approval comments

paperclip_list_approval_comments  { approvalId: "<id>" }

Look for prior reviewer notes. If a previous approver has already rejected this item and the resubmission did not address the stated concerns, note this — it affects the decision.