fabric-docs

Synchronize project documentation, docstrings, and ADRs with code reality.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adaw/skills --skill fabric-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabric-docs
Source: https://github.com/adaw/skills/tree/main/fabric-docs
Command: npx skills add https://github.com/adaw/skills --skill fabric-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ensures that your project's documentation accurately reflects the current codebase and recent changes, preventing knowledge gaps and integration issues.

Core Features & Use Cases

  • Synchronize Documentation: Updates docs, docstrings, and ADRs based on code reality.
  • Prevent API Drift: Ensures documentation doesn't invent APIs but reflects actual implementation.
  • Knowledge Accessibility: Keeps project knowledge organized and up-to-date.
  • Use Case: After merging a new feature that modifies an API, this skill automatically updates the relevant API documentation, ensuring developers have accurate information.

Quick Start

Update documentation to reflect the latest code changes.

Frequently Asked Questions about fabric-docs

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

FAQPage Schema
How do I keep documentation in sync with code after merging API changes?

Synchronizing documentation with code involves updating docs, docstrings, and Architecture Decision Records to match the actual codebase. This prevents API drift and ensures project knowledge remains accessible and accurate after recent code changes.

What is the best way to prevent API drift in project documentation?

Preventing API drift involves synchronizing documentation with the codebase to ensure docs reflect actual implementations rather than invented APIs. This prevents knowledge gaps and keeps project knowledge accessible and up-to-date.

How do I automatically update Architecture Decision Records based on code reality?

Updating Architecture Decision Records based on code reality involves synchronizing project documentation with the current codebase. This prevents drift between implementation and documentation, ensuring ADRs accurately reflect recent code changes.

Does synchronizing documentation with code update docstrings automatically?

Synchronizing documentation with code updates docstrings automatically based on code reality. This ensures knowledge accessibility and prevents drift between documentation and implementation across the project's codebase.

When do I need to synchronize documentation to prevent knowledge gaps?

You need to synchronize documentation when merging code changes that modify APIs, ensuring docs accurately reflect the current codebase. This prevents knowledge gaps and integration issues caused by outdated implementation references.