zenigame-fx-update-docs

Audit Alpha Factory docs against source code and update outdated terminology.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-fx-update-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zenigame-fx-update-docs
Source: https://github.com/kent013/zenigame-fx/tree/main/.claude/skills/zenigame-fx-update-docs
Command: npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-fx-update-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill audits Alpha Factory documentation against the current source code to detect outdated, missing, or undefined terminology, and updates the docs accordingly to maintain alignment with implementation.

Core Features & Use Cases

  • Automated drift detection between docs and source code to identify stale or missing entries.
  • Terminology alignment by verifying definitions across docs with the codebase and updating terminology in a central location.
  • Scope-driven updates using config-driven rules to apply changes selectively across docs/alpha_factory.

Quick Start

Run the zenigame-fx-update-docs skill with an optional scope to audit and update docs against the codebase.

Frequently Asked Questions about zenigame-fx-update-docs

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

FAQPage Schema
How do I detect documentation drift between source code and docs?

Documentation drift is detected by cross-checking source code against docs and central terminologies to identify outdated, missing, or undefined entries. This process audits Alpha Factory docs to maintain alignment with the current implementation.

How do I keep terminology consistent across multiple documentation files?

Terminology consistency is maintained by verifying definitions across docs with the codebase and updating terms in a central location. This ensures terminology alignment by enforcing standards that prevent hallucinations and undefined references.

Can I apply documentation updates to a specific scope instead of the whole repository?

Yes, scope-driven updates use config-driven rules to apply changes selectively. You can run the documentation audit across the repository scope or a specified scope, targeting updates specifically within docs/alpha_factory and related configurations.

What causes outdated or missing entries in Alpha Factory documentation?

Outdated or missing documentation entries occur when source code changes are not reflected in the docs. Automated drift detection audits the Alpha Factory docs against the codebase to identify these stale entries and update default references where needed.

Does documentation validation enforce standards to prevent hallucinations?

Yes, documentation validation enforces standards that prevent hallucinations, align terminology, and update default references. It cross-checks source code against docs to ensure no undefined terminology is introduced during updates.