One-click install
npx skills add https://github.com/ajbarea/techne --skill docsync-ajbarea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docsync
Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/docsync
Command: npx skills add https://github.com/ajbarea/techne --skill docsync-ajbarea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docs quickly fall out of date after refactors, leaving incorrect commands, paths, config keys, and version claims that waste time and cause broken workflows.

Core Features & Use Cases

  • Verifies checkable documentation claims: commands, file paths, function/class signatures, config keys/values, environment variables, version constraints, internal links/anchors, and documented exit codes/error messages.
  • Grounds fixes in the actual codebase: proposes corrections by reading the target repository’s implementation and conventions rather than rewriting based on guesswork.
  • Supports cross-repo doc auditing: validates docs that may live in a different repository than the current working directory by deriving the target repo root and loading the target’s skill context when available.

Quick Start

Run docsync on the file you want to verify, for example audit README.md or docs/*.md for drift and let it propose corrected text aligned to the current code.

Frequently Asked Questions about docsync

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

FAQPage Schema
How do I detect documentation drift in a markdown repository after refactoring?

Documentation drift is detected by verifying checkable claims like commands, file paths, and config keys against the actual codebase. The tool reads repository sources to identify outdated refactor artifacts and generates actionable proposed edits with line-level reporting.

Can I audit documentation that lives in a different repository than the code?

Cross-repo doc auditing validates markdown files located in a separate repository by deriving the target repository root and loading the target's context. This grounds the verification process in the correct remote codebase rather than the current working directory.

What types of documentation claims can be verified against the codebase?

Verifiable documentation claims include shell commands, file paths, function and class signatures, config keys and values, environment variables, version constraints, internal links, anchors, and documented exit codes or error messages.

How does the tool propose corrections for outdated markdown files?

Corrections for outdated markdown are proposed by reading the target repository's implementation, Makefile, runner, workflow, and config sources. It grounds fixes in actual codebase conventions rather than guesswork, providing line-level actionable edits.

What are the limitations when checking for outdated refactor artifacts in docs?

Checking for outdated refactor artifacts excludes non-checkable prose and generated-site artifacts from verification. It strictly targets measurable constraints like signatures and config keys, ensuring only traceable claims are validated against repository sources.