How do I install the Doc Sync skill?

Run npx skillmds@latest add sap-samples/doc-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Doc Sync skill do?

Audit AI guidance files (CLAUDE.md, copilot-instructions.md, .github/agents/, .github/prompts/) for consistency. Use after updating any AI-facing documentation. It is listed under Security on SkillMD.

Is Doc Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doc Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doc Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doc Sync?

sap-samples (@sap-samples) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doc Sync by sap-samples — Agent Skill

Name: Doc Sync
Author: sap-samples

File contents

Compare key facts across all AI guidance files and flag mismatches.

Files to Check

CLAUDE.md (primary, source of truth)
.github/copilot-instructions.md
.github/agents/parity-maintainer.agent.md
.github/prompts/add-parity-method.prompt.md
.github/prompts/release-checklist.prompt.md
.claude/agents/parity-reviewer.md
.claude/skills/parity-sync/SKILL.md
.claude/skills/release-check/SKILL.md

Facts to Verify Across Files

Package count — Three packages: hdb/, hdbext/, hdbhelper/. Any file that mentions "two packages" is stale.
Node.js engine constraints — hdb: ^20 || ^22 || ^24, hdbext: >=18.18.0. Cross-check against package.json.
Go version — Must match go.mod directive. Cross-check against go.mod.
Known API divergences — loadProcedurePromisified, callProcedurePromisified, hdb-only methods (destroyClient, validateClient, fetchSPMetadata, setSchema). Ensure all files that reference these agree.
Commands — npm test, npm run types, go test, go build, go vet. Verify referenced commands match package.json scripts and actual usage.
CI matrix — Node versions and Go version in .github/workflows/ci.yml should be consistent with documented constraints.

Output

Report a table:

File	Status	Issues
...	In sync / Drifted	specific mismatch

Then list recommended fixes with exact diffs.

Frequently asked questions

Doc Sync