mandoc-fix

Orchestrate mandoc -T markdown bug diagnosis, fix, and validation workflows.

14.2k|847|Updated Aug 30, 2013
One-click install
npx skills add https://github.com/idank/explainshell --skill mandoc-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mandoc-fix
Source: https://github.com/idank/explainshell/tree/main/.claude/skills/mandoc-fix
Command: npx skills add https://github.com/idank/explainshell --skill mandoc-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mandoc rendering bugs slow down the documentation workflow; this Skill orchestrates an end-to-end cycle to diagnose, fix, validate, and decide on promotion for rendering issues in mandoc, including interaction with subagents and evaluation tools.

Core Features & Use Cases

  • End-to-end bug-fix workflow orchestration for mandoc -T markdown rendering issues.
  • Dispatches a fresh subagent in the mandoc source tree, runs audit and compare, and guides promotion decisions.
  • Supports reproducibility with baseline rendering, audit, and step-wise validation across pages and rules. Use Case: A maintainer identifies a class of -T markdown rendering bugs and wants to coordinate diagnosis, fix, and verification.

Quick Start

Invoke the mandoc-fix workflow by describing the bug with /mandoc-fix and optional flags to tailor the audit and worktree.

Frequently Asked Questions about mandoc-fix

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

FAQPage Schema
How do I automate mandoc -T markdown rendering bug fixes end-to-end?

Mandoc bug fixes can be automated end-to-end by orchestrating diagnosis, fix application, validation, and promotion decisions. A reproducible workflow is established by dispatching a subagent within the mandoc source tree to handle rendering issues systematically.

How does subagent dispatching work for mandoc rendering bug diagnosis?

Subagent dispatching for mandoc bug diagnosis works by spinning up a fresh subagent in the mandoc source tree to execute baseline rendering and audits. This ensures reproducible step-wise validation across pages and rules before any fix promotion decision is made.

Do I need specific evaluation tools to validate mandoc markdown rendering fixes?

Validating mandoc markdown rendering fixes requires invoking /eval-render and /eval-llm as substeps within the workflow. These tools perform the audit and comparison needed to verify rendering outputs against baselines before deciding on promotion.

What is the best way to coordinate mandoc bug fixes across a source tree?

The best way to coordinate mandoc bug fixes across a source tree is using an orchestrated workflow that handles diagnosis, fix application, and verification. It sets up a reproducible environment, dispatches a subagent for isolated work, and runs audits to guide promotion decisions.

Why does mandoc -T markdown rendering require an audit before promotion?

Mandoc -T markdown rendering requires an audit and validation before promotion to ensure the fix does not introduce regressions. The workflow performs step-wise validation across pages and rules, comparing outputs against a baseline to confirm the rendering issue is resolved safely.