docs-alignment

Align repository documentation with current code, workflow, and governance behavior.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cheetah-alo/NegritaOS --skill docs-alignment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-alignment
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/docs-alignment
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill docs-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents documentation drift by ensuring repository guidance always matches the actual behavior of code, workflows, rules, and governance.

Core Features & Use Cases

  • Behavior-to-Documentation Alignment: Ensures docs describe current behavior, not intended or outdated behavior, during any contributor-facing change.
  • Consistency Guardrails: Detects and prevents contradictions between .codex system files, rules, profiles, prompts, and skills.
  • Deprecation Cleanup: Removes references to deprecated files, routes, scripts, or workflows so users aren’t misled.

Quick Start

Use this skill when you update an API, workflow, rule, or contributor guide and want to validate that the repository documentation still matches reality.

Frequently Asked Questions about docs-alignment

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

FAQPage Schema
How do I prevent documentation drift when updating repository workflows?

Documentation drift occurs when repository guidance no longer matches actual code or workflow behavior. Aligning docs with current behavior prevents contributors from following outdated paths, commands, or deprecated references during updates.

What is the best way to check consistency between .codex files and repository rules?

Checking consistency between .codex files and rules requires detecting contradictions across system files, profiles, prompts, and skills. Consistency guardrails prevent conflicts and ensure internal alignment within the repository.

How do I update contributor guides to remove deprecated API routes and scripts?

Updating contributor guides involves removing references to deprecated files, routes, scripts, or workflows. Deprecation cleanup ensures users are not misled by outdated commands and paths that no longer execute.

Can I validate that repository documentation paths and commands are still executable?

Yes, validating executable paths and commands maintains internal consistency within .codex and rules. This validation satisfies requirements to ensure repository guidance matches actual behavior and removes deprecated references.

When do I need to align repository documentation with governance changes?

You need to align documentation with governance changes whenever contributor-facing changes occur. This ensures repository guidance matches actual behavior across rules, profiles, prompts, and skills without contradictions.