docs-manager

Synchronize repository documentation and Graphify artifacts across raw/ and graphify-out/.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill docs-manager-pko89403
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-manager
Source: https://github.com/pko89403/ZeroAlign-Rec/tree/main/.agents/skills/docs-manager
Command: npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill docs-manager-pko89403

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized capability to maintain the repository documentation and the Graphify source corpus, ensuring raw/ and graphify-out/ stay aligned and up-to-date.

Core Features & Use Cases

  • Synchronize raw/ source documents with graphify-out/ artifacts to keep knowledge layers aligned.
  • Review Graphify artifacts and sync core docs like README.md, AGENTS.md, and harness instructions across the repository (including .github/copilot-instructions.md, .agents/policies/local-adaptation.md, and .agents/skills/graphify-manager/SKILL.md).
  • Perform full docs/harness sync after code changes to reflect ongoing updates.

Quick Start

Run the docs-manager to refresh raw/, review graphify-out/GRAPH_REPORT.md, and align root documents across the repo.

Frequently Asked Questions about docs-manager

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

FAQPage Schema
How do I synchronize repository documentation with my Graphify harness output?

You can synchronize repository documentation with your Graphify harness output by aligning the source documents in raw/ with the generated artifacts in graphify-out/ to keep all knowledge layers up to date.

What is the best way to keep README.md and AGENTS.md aligned across a repository?

Keeping README.md and AGENTS.md aligned across a repository requires applying coordinated synchronization rules to preserve cross-file references and versioned outputs after code changes occur.

Does docs-manager require access to the repository root to sync harness instructions?

Yes, syncing harness instructions requires access to the repository root to properly coordinate synchronization rules across core documents like .github/copilot-instructions.md and local adaptation policies.

How do I perform a full docs and harness sync after code changes?

Perform a full docs and harness sync after code changes by refreshing the raw/ directory, reviewing the graphify-out/GRAPH_REPORT.md artifacts, and aligning root documents across the repository.

Why does my Graphify artifact review show misaligned cross-file references?

Graphify artifact reviews show misaligned cross-file references when raw/ documentation maintenance and graphify-out/ outputs diverge, requiring coordinated synchronization rules to restore versioned output alignment.