code-documentation

Write, update, route, and reconcile repository documentation across multiple surfaces.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/alvarovillalbaa/plugins --skill code-documentation-alvarovillalbaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-documentation
Source: https://github.com/alvarovillalbaa/plugins/tree/main/engineering/skills/code-documentation
Command: npx skills add https://github.com/alvarovillalbaa/plugins --skill code-documentation-alvarovillalbaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates stale, missing, or conflicting documentation by helping you create, update, move, and verify the right docs as the codebase evolves.

Core Features & Use Cases

  • Doc contract ownership: ensures repository documentation stays coherent over time and maintains a single source of truth.
  • Smart doc routing and conflict handling: places new information into the narrowest appropriate surface (inline, in-folder, root instructions, living docs, or historical timestamped evidence) and resolves live-vs-historical drift by moving or removing misplaced docs.
  • Full documentation website generation: runs an end-to-end workflow to research a project and scaffold a polished Nextra site (including supporting references and templates) when external users need searchable docs.
  • Command-driven workflows: supports focused doc operations for specific changes or areas, plus a complete /docs-site flow for project-level documentation.

Quick Start

Use the code-documentation skill when you need to update docs for a change request, for example: ask it to refresh documentation for the repository area affected by your last commit.

Frequently Asked Questions about code-documentation

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

FAQPage Schema
How do I keep repository documentation accurate and current as my codebase evolves?

To keep repository documentation accurate, you can use a doc maintenance workflow that updates inline, in-folder, and living docs while enforcing Last updated rules to eliminate stale or conflicting content.

What's the best way to generate a documentation website for external users?

The best way to generate a documentation website for external users is running an end-to-end workflow that researches your project and scaffolds a polished Nextra site with supporting references and templates.

How does smart doc routing handle conflict resolution between living and historical docs?

Smart doc routing handles conflict resolution by placing new information into the narrowest appropriate surface, detecting live-vs-historical drift, and moving or removing misplaced docs to maintain a single source of truth.

Can I refresh technical writing for a specific repository area instead of the whole project?

Yes, you can refresh technical writing for a specific repository area using command-driven workflows that target focused doc operations for individual changes rather than generating a complete project-level documentation site.

When do I need timestamped documentation surfaces in my repository?

You need timestamped documentation surfaces when preserving historical evidence of changes, allowing the system to reconcile live docs against historical records and move outdated information into correctly placed timestamped artifacts.