techdoc-writer

Provide the git repository, debug logs, and session context, then request a formal document. The Skill collects commits and logs, classifies the document type, drafts a chapter outline for your confirmation, and writes the full document with real diffs and verbatim log quotes.

The Skill applies the Rockchip skeleton by default: preface with revision history, Chapter-N numbered body, and appendix with glossary and references. You can also supply a reference PDF whose structure and tone it will extract and follow instead.

Yes. When given a Feishu link or asked to write to Feishu, it operates through the lark-doc skill and creates diagrams as Feishu whiteboards via lark-whiteboard. Without a Feishu target, it writes a local Markdown file using standard Markdown syntax.

A fault diagnosis chapter appears only for debugging retrospectives or qualified mixed documents where fixes actually landed. Design docs, architecture proposals, and unimplemented guides never get a fault chapter, and trivial code typos are excluded from it.

Solutions must be verifiable, so code changes are extracted from actual commits via git show and split by hunk into the relevant sections. Rewritten-from-memory code cannot be cross-checked by readers and is not accepted.

Three lint scripts check phrasing rules, format mixing between Feishu and Markdown, and inline code wrapping of technical identifiers. After scripts pass, the AI still reads the full draft to catch duplication, broken references, and numbering gaps that scripts cannot detect.