sync-agents-md

Refresh AGENTS.md by comparing it against repository evidence sources.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nclandrei/dotfiles --skill sync-agents-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-agents-md
Source: https://github.com/nclandrei/dotfiles/tree/main/config/skills/sync-agents-md
Command: npx skills add https://github.com/nclandrei/dotfiles --skill sync-agents-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps AGENTS.md up to date by anchoring its content to real repo evidence, enabling reliable maintenance and automation.

Core Features & Use Cases

  • Drift-detection: compares AGENTS.md against repository sources (logs, workflows, READMEs, architecture notes) to surface only evidence-based updates.
  • Automated updates: updates or annotates sections with verified changes while preserving style and intent.
  • Audit trail: records a memory entry detailing paths reviewed, changes made, sections skipped, and any blockers, plus a concise summary suitable for inbox reports.

Quick Start

Run the sync-agents-md workflow to refresh AGENTS.md using the latest repository evidence.

Frequently Asked Questions about sync-agents-md

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

FAQPage Schema
How do I keep AGENTS.md up to date with repository evidence?

To keep AGENTS.md up to date, you can run an automated sync workflow that compares the file against repository sources like logs, workflows, and READMEs to surface evidence-based updates.

What causes documentation drift in an AGENTS.md file?

Documentation drift occurs when AGENTS.md content becomes outdated because repository source files like architecture notes and workflows change independently without triggering a corresponding documentation refresh.

How do I automate AGENTS.md maintenance without losing my formatting?

Automate AGENTS.md maintenance using drift-detection workflows that apply verified updates from repository sources while preserving the original style and intent of the existing documentation sections.

Can I generate an audit trail for AGENTS.md updates?

Yes, you can generate an audit trail by recording a memory entry that details the paths reviewed, changes made, sections skipped, and blockers encountered during the AGENTS.md sync process.

What's the best way to detect content drift across multiple repositories?

The best way to detect content drift is to run periodic maintenance workflows that compare AGENTS.md against source-of-truth files across repositories, ensuring only evidence-based changes are applied.