Manage reviews

Skill indranilbanerjee/socialforge/skills/manage-reviews

Open-source agency-grade social media production plugin — 16 skills, 25 commands, AI image (Nano Banana Pro) + AI video (Kling v3.0 Pro) + C2PA signing (EU AI Act Article 50). Installs on Claude Code, Cowork, Codex, Cursor, Copilot CLI, Antigravity. By Indranil Banerjee (indranil.in).

Install

npx -y skills add indranilbanerjee/socialforge --skill manage-reviews

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Handle approval workflows — internal review, client review, CEO approval, revision requests.

SKILL.md

1.9 KB, as published. Nobody here has run it

/socialforge:manage-reviews — Review & Approval Manager

Manage the multi-tier approval workflow per brand's approval-chain.json.

Approval Tiers

HERO content: Internal review → Client approval → CEO approval (if configured)
HUB content: Internal review → Client approval (optional)
HYGIENE content: Internal review only (auto-approvable if configured)

Actions

/socialforge:manage-reviews --approve P04 — Approve post P04 at current tier
/socialforge:manage-reviews --revise P04 "Make the background warmer" — Request revision with feedback
/socialforge:manage-reviews --client-send — Send all internally-approved posts to client review
/socialforge:manage-reviews --check — Check pending approvals and send reminders

State Transitions

QUEUED → ASSET_MATCHING → GENERATING → PENDING_REVIEW PENDING_REVIEW → APPROVED_INTERNAL | REVISION_REQUESTED | REJECTED REVISION_REQUESTED → GENERATING (re-enters production with feedback) REJECTED → QUEUED (start over) APPROVED_INTERNAL → PENDING_CLIENT (if client review required) | FINAL (if not) PENDING_CLIENT → APPROVED_CLIENT | REVISION_REQ_CLIENT | REJECTED_CLIENT APPROVED_CLIENT → PENDING_CEO (if CEO required) | FINAL (if not) PENDING_CEO → APPROVED_CEO → FINAL FINAL → (write-protected, no transitions)

Rules

FINAL status is write-protected — cannot be modified after finalization
Revision requests re-enter the generation pipeline with specific feedback
Max 3 revision cycles per HERO post before escalation
Reminders sent via Slack/email after N days (per escalation_rules)