editorial-approve

Apply approved content versions to specified sites and slugs without git operations.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-approve
Source: https://github.com/oletizi/audiocontrol.org/tree/main/.claude/skills/editorial-approve
Command: npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires editorial-review, editorial.

What problem does it solve?

Finalize content review cycles by applying the approved version to the correct place, while preserving the single-source-of-truth and ensuring that no Git operations are executed during approval.

Core Features & Use Cases

  • Validates the workflow state, resolves the approved version from the latest approve annotation, and transitions the workflow to applied.
  • For longform content, no disk write is performed because the on-disk article already holds the approved content.
  • For shortform content, updates the matching DistributionRecord in the editorial calendar with the approved copy.

Quick Start

Run /editorial-approve <slug> [--site <site>] [--platform <p>] [--channel <c>] to finalize the approved content for your workflow.

Frequently Asked Questions about editorial-approve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finalize approved content in an editorial workflow without Git operations?

To finalize approved content without Git, apply the approved version to the specified site and slug. The workflow resolves the latest approve annotation and transitions the state to applied using internal utilities.

What is the difference between applying longform and shortform editorial approvals?

For longform content, applying the approval validates the version against the workflow without disk writes, as the on-disk article already holds the content. For shortform content, it updates the DistributionRecord in the editorial calendar.

How do I update the DistributionRecord in an editorial calendar for shortform content?

To update a DistributionRecord for shortform content, run the approval process with the correct slug, platform, and channel parameters. This matches the approved copy to the corresponding calendar entry.

Does the editorial approval process require Git operations to apply changes?

No, the editorial approval process does not require Git operations. It preserves the single-source-of-truth by resolving the latest approve annotation and transitioning the workflow state internally.

How do I validate an approved version against my current content workflow state?

Validating an approved version requires the editorial-approve utility to check the latest approve annotation against the current workflow. It ensures the single-source-of-truth is maintained before transitioning to applied.

Can I finalize blog content approvals for specific platforms and channels?

Yes, you can finalize blog content approvals for specific platforms and channels. Specify the target site, platform, and channel parameters alongside the slug to apply the approved version correctly.