copy-editor

Audit repository copy for typographic correctness using deterministic pattern-based rules.

18|3|Updated Mar 28, 2026

Search Tags:#automation #typography #review #style-guide #lockfile #copy-editor

Ready to run

npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill copy-editor-ondrej-svec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: copy-editor
Source: https://github.com/ondrej-svec/heart-of-gold-toolkit/tree/main/plugins/marvin/skills/copy-editor
Command: npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill copy-editor-ondrej-svec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires js-yaml.

What problem does it solve?

Copy-editing at scale is error-prone and time-consuming. This Skill provides deterministic typography auditing and editorial recommendations to ensure consistency with repo-local style guides.

Core Features & Use Cases

Deterministic Layer 1 typography checks that auto-close when rules pass.
Human-focused Layer 2 suggestions for Czech and English content across code-like and prose surfaces.
Lockfile-based segmentation to preserve reproducibility and support PR review of changes.

Quick Start

Run the audit with your .copy-editor.yaml to generate Layer 1 findings and a pending Layer 2 review.

Frequently Asked Questions about copy-editor

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

FAQPage Schema

How do I automate typography checks for Markdown and JSON content in a repository?▼

You can automate typography checks by running a deterministic pattern-based audit across Markdown, JSON, and code-like content. This surfaces Layer 1 typography findings that auto-close when rules pass, plus Layer 2 editorial recommendations for human review.

What is a lockfile-based segmentation gate in copy-editing audits?▼

A lockfile-based segmentation gate preserves reproducibility by tracking audited content segments, supporting PR review of typography changes and ensuring deterministic audit results across runs.

Can I audit Czech and English typography simultaneously in the same repository?▼

Yes, the audit supports Czech and English contexts across code-like and prose surfaces, applying deterministic Layer 1 typography checks and generating human-focused Layer 2 editorial suggestions for both languages.

How do I configure repository copy-editing rules using frontmatter and YAML?▼

You configure rules by creating a .copy-editor.yaml file that drives frontmatter-based configuration. The audit reads this style guide to apply deterministic typography checks and generate structured outputs for machine consumption and human review notes.

Does the typography audit work with existing CI workflows and PR review processes?▼

The audit produces structured outputs suitable for machine consumption and uses a lockfile-backed segmentation gate to support PR review of changes, making it compatible with CI workflows for deterministic typography auditing.

Why use deterministic pattern-based rules instead of AI for copy-editing at scale?▼

Deterministic pattern-based rules ensure reproducible typography audits that auto-close when rules pass, avoiding the variability of AI suggestions while still providing Layer 2 editorial recommendations for human review.