What is evidence-first documentation?

It is an approach where documentation is derived directly from extracted code evidence before updating higher-level documents, ensuring the source of truth is always grounded in the current codebase.

How does DocOps Sync handle documentation drift?

The skill compares current code evidence against existing docs and logs any detected conflicts or inconsistencies to a mandatory conveyor-gaps.md file for developer review.

Which documentation types are supported by this skill?

It is designed to update a complete documentation chain including SPECs, REFs, HOWTOs, and RUNBOOKs, ensuring each links back to the relevant code evidence.

Can I run this without a full context preflight?

Yes, while context preflight is recommended, the skill is designed to warn and proceed even if preflight fails, ensuring documentation synchronization isn't blocked.

DocOps Documentation Sync

Name: DocOps Documentation Sync
Author: murillodutt

bymurillodutt

0•

学習とドキュメンテーション

Synchronizes source code evidence with derived technical documentation to prevent drift and ensure accurate specifications.

DocOps Sync is a specialized skill designed to automate the maintenance of project documentation by extracting real-time evidence from source code. It ensures that technical specifications (SPECs), references (REFs), tutorials (HOWTOs), and operational guides (RUNBOOKs) remain accurate and linked to the actual implementation. By identifying drift and logging conflicts in a centralized gaps file, the skill prevents documentation from becoming stale and maintains a verifiable chain of truth between development and documentation, making it essential for teams managing complex Nuxt 4 or general JavaScript/TypeScript stacks.

主な機能

01Resilient execution that warns rather than blocks if context preflight fails

02Evidence-first update flow ensures documentation is always grounded in actual source code

03Mandatory logging of detected gaps to a centralized conveyor-gaps file

04Automatic drift detection identifies conflicts between code and existing documentation

05Traceable documentation linking that connects derived guides back to source evidence

060 GitHub stars

ユースケース

01Auditing documentation debt by identifying drift between implementation and design docs

02Updating technical specifications and runbooks immediately after a major code refactor

03Ensuring internal HOWTO guides remain functionally accurate as the codebase evolves

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add murillodutt/cellm sync

For use in Claude.ai and ChatGPT