gendoc-align-fix

Parse ALIGN_REPORT.md and apply severity-sorted alignment fixes across documentation layers.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ibalasite/gendoc --skill gendoc-align-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gendoc-align-fix
Source: https://github.com/ibalasite/gendoc/tree/main/skills/gendoc-align-fix
Command: npx skills add https://github.com/ibalasite/gendoc --skill gendoc-align-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

讀取 align-check 報告,依指定 layer 自動修復對齊問題,並在修復完成後輸出 Fix Summary 與更新修復狀態。

Core Features & Use Cases

  • 自動解析 ALIGN_REPORT.md,根據 layer 與 severity 進行排序與優先級判斷
  • 根據上游/下游的修復策略自動修復文件,並在修復後輸出修復清單與摘要
  • 修復完成後自動更新 ALIGN_REPORT.md 的修復狀態,確保長期追蹤與一致性
  • 支援多層級修復場景:docs、doc-code、code-test、doc-test、all,並可指定特定 layer
  • 呼叫時機:在 align-check 完成、或使用者請求修復時觸發修復流程

Quick Start

呼叫 /gendoc-align-fix docs 以自動修復 docs 層的對齊問題。

Frequently Asked Questions about gendoc-align-fix

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

FAQPage Schema
How do I automatically fix documentation alignment issues across upstream and downstream layers?

To automatically fix documentation alignment issues, you can use a tool that parses an alignment report and applies upstream or downstream fixes across specified layers like docs, doc-code, code-test, or all layers. It sorts findings by severity, verifies each fix before commit, and updates the report with FIXED markers.

What is the best way to resolve doc-code and code-test alignment discrepancies after a consistency check?

The best way to resolve doc-code and code-test alignment discrepancies is to parse the generated alignment report, prioritize findings by severity, and apply targeted upstream or downstream repairs. The process verifies each fix before committing and marks resolved items in the report for long-term tracking.

How do I ensure my documentation fixes are verified before committing changes?

To ensure documentation fixes are verified before committing changes, use an automated alignment repair workflow that checks each applied fix against the alignment report. It only commits verified changes and automatically updates the report status with FIXED markers to maintain consistency.

Can I target a specific layer for alignment fixes instead of repairing all documentation layers at once?

Yes, you can target a specific layer for alignment fixes instead of repairing all layers at once. The repair process supports individual layers such as docs, doc-code, code-test, and doc-test, allowing you to isolate fixes and apply upstream or downstream repairs only where needed.

When should I trigger an automated alignment repair workflow for my documentation?

You should trigger an automated alignment repair workflow immediately after completing a consistency alignment check, or whenever you need to resolve detected upstream and downstream documentation discrepancies. This ensures that all identified issues are sorted by severity and systematically repaired before final commit.

Does the alignment repair process update the original consistency report after applying fixes?

Yes, the alignment repair process updates the original consistency report after applying fixes. Once a fix is verified and committed, the tool automatically annotates the alignment report with FIXED markers, ensuring long-term tracking and maintaining consistent documentation quality across all layers.