Define field-by-field source authority
Define field-by-field source authority rather than one universal source of truth.
sync-project-metadata
skill
Agent skill for Codex and Claude Code that audits and synchronizes project metadata across manifests, documentation, releases, and catalogs.
- Role
- Agent workflow design and automation engineering
- Scope
- Agent workflow, validation automation, and packaging
- Status
- Published npm package
Problem
Project identity and version details are duplicated across files and drift, leaving users with broken links, wrong install commands, or conflicting compatibility claims.
Constraints
- C1
Each field has a different authoritative source.
- C2
A human-facing description must match implemented behavior, not merely manifest prose.
- C3
Local synchronization does not authorize publishing or changing remote metadata.
Architecture
Evidence/source precedence model; deterministic metadata auditor and reconciliation workflow; repository-native validation plus npm distribution.
01
Skill workflow
Evidence/source precedence model.
02
Automation
Deterministic metadata auditor and reconciliation workflow.
03
Verification
Repository-native validation plus npm distribution.
Decisions
Report ambiguity
Report ambiguity instead of overwriting uncertain values.
Validate every downstream consumer after edits
Validate every downstream consumer after edits.
Contribution
- Encoded canonical-source rules.
- Built metadata drift detection.
- Designed scoped local synchronization and validation reporting.
- Added safe installation and package tests.
Outcomes
- Agents can identify conflicting names/versions/URLs.
- Repair authorized local copies.
- Preserve unknowns for manual resolution.
- Report remaining remote actions separately.
Verified stack
- Agent Skills
- JavaScript
- Node.js
- npm
- GitHub Actions
- CI/CD
Working through something similar?
Share your challenge, scope, and timeline to start a focused conversation.