Doc Synchronization

Autonomous Documentation & Skill Synchronization Engine

This skill establishes the Zero-Reminder Automatic Synchronization Rule: whenever ANY code, API, database schema, workflow, or architecture change is introduced or modified in the repository, all corresponding architectural documents, API references, READMEs, changelogs, and AI agent skills (.agents/skills/) MUST be automatically inspected, updated, and expanded by the agent without requiring any prompting or reminders from the human user.

1. High-Priority Rule: Zero-Reminder Automatic Synchronization

[!IMPORTANT] AUTONOMOUS DOCUMENTATION & SKILL UPDATES (No Human Prompting Needed):

• AI agents are strictly required to treat Agent Skills (.agents/skills/) and Documentation (docs/, README.md, CHANGELOG.md) as first-class codebase artifacts.
• Every feature addition (feat), improvement (perf/refactor), bug fix (fix), database migration (db), or DevOps pipeline (ci) MUST automatically trigger a synchronization pass across relevant skills and markdown specifications before finalizing commits.
• The human developer should NEVER have to ask: "please update the docs" or "please update the agent skills". This is a mandatory, automated built-in reflex.

2. Subsystem-to-Skill & Documentation Synchronization Matrix

Whenever modifying files in any subsystem, the agent MUST automatically update the corresponding documentation and skill files:

3. Autonomous Skill Creation & Evolution Rule

• When to Create a New Agent Skill (.agents/skills/<name>/SKILL.md):
  • Whenever introducing a new architectural pattern, operational domain, or subsystem that future AI agents must interact with or maintain (e.g. saas-and-mcp-architecture, git-post-merge-cleanup, cli-tooling-guide).
  • Format: Include YAML frontmatter (name, description) and comprehensive operational guidelines, rules, and example commands.
• When to Update Existing Skills:
  • Whenever modifying runtime behaviors, adding flags to scripts, updating CLI commands, or changing deployment configurations.
  • Keep skills concise, actionable, and strictly synchronized with the live implementation.

4. Pre-Commit Autonomous Synchronization Checklist

Before executing git commit or finalizing any milestone, execute this 4-step checklist:

1. Inspect Staged/Modified Files:

   git status --short
   

2. Cross-Reference Subsystem Matrix: Identify all target docs and agent skills impacted by the modified files.
3. Apply Documentation & Skill Edits: Update markdown files and skills with exact details.
4. Log in Changelog: Add concise bullet points under ## [Unreleased] in CHANGELOG.md.
5. Sync Skills Upstream: If any skill inside .agents/skills/ was added or modified, execute skills-sync push (or make skills-push) to propagate updates to MishraShardendu22/agent-skills.