wiki-update

Generate PR-ready wiki updates and changelogs for completed tasks.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/nholder88/ai-agent-workflows --skill wiki-update-nholder88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-update
Source: https://github.com/nholder88/ai-agent-workflows/tree/main/skills/wiki-update
Command: npx skills add https://github.com/nholder88/ai-agent-workflows --skill wiki-update-nholder88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of user-facing wiki updates and changelog entries after a completed task, applying deterministic eligibility rules, host-scope checks, and producing PR-ready documentation including how-to guides and end-user guidance.

Core Features & Use Cases

  • Deterministic eligibility and policy-driven decisioning to determine when wiki updates should be generated.
  • PR-ready documentation artifacts including changelog entries and user-facing how-to guides.
  • Host-scope enforcement (GitHub.com and allowed GHES hosts) to ensure documentation updates stay within approved environments.
  • Structured output payloads and metadata suitable for integration into code review pipelines.
  • Clear guardrails and failure handling to avoid pipeline disruption and provide actionable audit information.

Quick Start

Point me at a completed Stage 7 PASS task and I will generate PR-ready wiki updates and changelog entries.

Frequently Asked Questions about wiki-update

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

FAQPage Schema
How do I generate PR-ready changelog entries after completing a GitHub task?▼

You can generate PR-ready changelog entries by pointing the automation at a completed Stage 7 PASS task. It applies deterministic eligibility rules and host-scope checks to produce structured documentation artifacts for your GitHub workstreams.

What is the best way to automate user-facing wiki updates for completed tasks?▼

Automating user-facing wiki updates requires applying policy-driven decisioning to completed tasks. This skill generates structured output payloads containing how-to guides and end-user guidance suitable for integration into code review pipelines.

Does wiki-update work with self-hosted GitHub Enterprise environments?▼

Yes, wiki updates support GitHub.com and allowed GHES hosts. Host-scope enforcement ensures documentation updates stay within approved environments, preventing pipeline disruption and providing actionable audit information.

Can I integrate automated changelog generation directly into my code review pipeline?▼

Yes, the automation outputs structured payloads and metadata designed for integration into code review pipelines. It includes clear guardrails and failure handling to avoid pipeline disruption while producing PR-ready documentation artifacts.

When should I use automated documentation generation over manual wiki updates?▼

Automated documentation generation is ideal when you need deterministic eligibility classification and policy-driven decisioning for completed Stage 7 PASS tasks. It enforces host-scope policy and requires human approval before finalizing PR-ready wiki updates.

Why does wiki update generation require human approval before creating a pull request?▼

Human approval is required to validate the generated documentation payload before it becomes a pull request. This guardrail ensures the automated changelog entries and how-to guides meet quality standards while maintaining an actionable audit trail.