sync-rule

Mirror shared rule file edits between a consumer project and the tech-agency plugin.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill sync-rule-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-rule
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/sync-rule
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill sync-rule-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Shared policy rules are copied from the tech-agency plugin into a consumer project's .claude/rules/shared/ directory, and edits on either side silently diverge with no mechanism to reconcile them. This Skill detects changed shared-rule files, diffs them against their mirror, and applies the edit to the other side so the two repositories stay consistent. ## Core Features & Use Cases - Bidirectional mirroring: Sync edits from a consumer repo up to tech-agency, or propagate canonical tech-agency updates down to consumers using identity path mapping under rules/shared/. - Genericization on upstream sync: Flags project-specific identifiers (app names, module paths, ticket IDs, commit hashes) and replaces them with placeholders before writing to the public tech-agency repo, with user approval required. - Drift detection and integrity checks: The bundled mirror.sh script verifies the consumer mirror against a SHA-256 manifest (check), refreshes it (pull), and reports differences (diff, status), refusing to silently shrink the mirror. - Use Case: After editing .claude/rules/shared/board-in-pr.md in your project, run the sync to apply the same change to the canonical tech-agency checkout, with consumer-specific names stripped before commit. ## Quick Start Sync my edited shared rule in .claude/rules/shared/ to the tech-agency plugin and show me the diff before applying it.

Frequently Asked Questions about sync-rule

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

FAQPage Schema
How do I sync shared rules between my project and the tech-agency plugin?▼

Edit the rule under .claude/rules/shared/ in your consumer repo, then invoke the sync-rule skill. It locates the tech-agency side via CLAUDE_PLUGIN_ROOT, TECH_AGENCY_PATH, or the plugin cache, shows the diff, and applies the change to the mirror file.

How do I check if my copied rules have drifted from the plugin?▼

Run mirror.sh check from the skill directory. It compares each mirrored file's SHA-256 hash against the .synced-from manifest and reports edited or missing files, exiting non-zero on drift.

Does sync-rule sync the language coding standards too?▼

No. The 8 language coding standards live only in the plugin and are read on demand; they are never copied or mirrored. A local copy of a coding standard in a consumer repo is drift and should be deleted.

What happens to project-specific names when syncing to tech-agency?▼

The skill flags consumer-specific identifiers such as app names, module paths, ticket IDs, and commit hashes, then proposes generic replacements. It shows an annotated diff and waits for your approval before applying any genericization.

Why does mirror.sh pull refuse to refresh my rules?▼

The pull command refuses to shrink the mirror when the resolved source has fewer files than the current manifest, which usually means it resolved to an older released version. Set TECH_AGENCY_RULES to the intended source or use MIRROR_FORCE=1 to override.