wf-finish

Compiles active WikiFlow changes into current, history, deprecated, and decision documents.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/liqunx/wikiflow --skill wf-finish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-finish
Source: https://github.com/liqunx/wikiflow/tree/main/skills/wf-finish
Command: npx skills add https://github.com/liqunx/wikiflow --skill wf-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

在文档驱动的开发流程中,active 目录里的变更需要被稳定地编译到 Wiki 知识库,否则文档会与代码实现脱节,历史版本与决策记录也难以保持一致。

Core Features & Use Cases

  • Wiki 编译与版本归档:将 spec.md / tasks.md / decisions.md 的变更合并到 current/,并把旧版本移动到 history/,控制保留数量。
  • 废弃功能迁移与索引更新:对 spec.md 中标记为“废弃”的内容生成 deprecated/ 页面,同时更新 index.md 中 current / history / deprecated / decisions 的列表与统计。
  • 决策日志结构化:把 decisions.md 解析为独立决策文件,固化每个“为什么”的可追溯信息。
  • 自动 Lint 检查:执行废弃文档检查、失效链接检查、重复与一致性检查、孤岛页面检查和历史清理,并对需人工确认的项进行提示。

Quick Start

在文档仓库中运行 /wf-finish,把 active 里的变更编译到 docs/wiki,并自动更新 current、history、deprecated 与 decisions,同时执行 lint 校验。

Frequently Asked Questions about wf-finish

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

FAQPage Schema
How do I compile Wiki changes into a documentation repository while archiving previous versions?

The workflow compiles active WikiFlow changes into the documentation repository by generating updated current pages, archiving previous versions into history, extracting deprecated content, and splitting decisions into dedicated documents.

How does decision log extraction work for documentation-first AI development workflows?

Decision log extraction works by parsing decisions.md into independent decision documents, structuring the reasoning behind each choice. This fixes traceable 'why' information into dedicated files within the Wiki's structured knowledge base.

Can I run lint validation on my documentation repository to detect orphan pages and broken links?

Yes, you can run lint validation on your documentation repository to detect orphan pages and broken links. The lint checks include link validity, consistency, orphan detection, and deprecated content checks, prompting for manual confirmation where needed.

Does the Wiki compilation workflow require a specific configuration file to run?

Yes, the Wiki compilation workflow requires reading the .wikiflow/config.json file to determine paths and language settings. This enforces the documentation-repository execution constraint and ensures idempotent compilation across the structured knowledge base.

What is the best way to handle deprecated content migration in a documentation knowledge base?

The best way to handle deprecated content migration is to generate dedicated deprecated pages from spec.md markers and update the index.md lists. This isolates outdated features while maintaining accurate statistics across current, history, and decision directories.

Why does my idempotent workflow fail to update the index.md statistics after archiving history?

An idempotent workflow might fail to update index.md statistics if the documentation repository execution constraint is not properly enforced or lint checks detect consistency issues. Ensure .wikiflow/config.json paths are correct and history retention limits are configured.