edi-finalize

Run structured post-writing QA checks using STYLE.md and EDITORIAL.md rules.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-finalize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edi-finalize
Source: https://github.com/Telepotch/hirano-edi-on-claude-code/tree/main/.claude/skills/edi-finalize
Command: npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-finalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The post-writing QA workflow ensures manuscript quality by separating the author from the reviewer and executing a structured editorial QA after drafting.

Core Features & Use Cases

  • Enforces a formal QA pass after writing to catch style, consistency, and factual gaps.
  • Coordinates between writers and editors by outlining checks and logging outcomes.
  • Supports project-specific rules via STYLE.md and EDITORIAL.md and can incorporate lexical guidance from LEXICON if available.

Quick Start

Trigger the post-writing QA workflow to audit and polish the manuscript.

Frequently Asked Questions about edi-finalize

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

FAQPage Schema
How do I automate editorial QA for a manuscript before publication?

Editorial QA automation runs a structured post-writing pass that audits drafts for style consistency, factual gaps, and adherence to project rules before publication. It coordinates between writers and editors by logging structured checks and outcomes.

What is a post-writing QA workflow and when should I use it?

A post-writing QA workflow is a formal review process that separates authoring from editorial checking. Use it after drafting to catch style or consistency issues, ensuring manuscript quality is verified before final publication.

How do I enforce style guidelines and a lexicon during manuscript finalization?

Manuscript finalization enforces style guidelines by requiring defined STYLE.md and EDITORIAL.md rules. It optionally integrates a LEXICON file to provide specific lexical guidance during the quality assurance checks.

Can I use this editorial QA workflow for collaborative writing and editing projects?

Yes, the editorial QA workflow supports collaborative writing and editing projects by coordinating checks between writers and editors, logging outcomes, and applying project-specific style rules to shared drafts.

Do I need specific configuration files to run a manuscript style-check?

Yes, manuscript style-checks require adherence to defined STYLE.md and EDITORIAL.md rules to execute properly. A LEXICON file is optional but can be integrated for additional lexical guidance.