skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
laurigates/claude-plugins55 installs

blueprint-sync

Check for stale generated content and offer regeneration or promotion. Use when syncing blueprint after PRD changes, or reconciling .claude/rules/ drift.

How do I install this agent skill?

npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-sync
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubwarn

    The skill manages and synchronizes generated content by comparing file hashes against a manifest. It uses shell commands to perform these checks, which presents a risk of command injection if the manifest file contains malicious filenames. Additionally, it reads project files that could contain instructions intended to influence the agent's behavior (indirect prompt injection).

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    1/1 file flagged

What does this agent skill do?

Check the status of generated content and offer options for modified or stale files.

When to Use This Skill

Use this skill when...Use blueprint-promote instead when...
You want to detect stale or modified generated rules/skillsYou've decided to keep one specific edited rule (single artifact)
You're reconciling drift between .claude/rules/ and the manifestYou want to acknowledge modifications and stop sync warnings
You want regenerate/promote/keep options for many files at onceUse blueprint-generate-rules instead to (re)generate from PRDs
You preview status with --dry-run before changing anythingUse blueprint-sync-ids instead for ID assignment, not content drift

Flags

FlagDescription
--dry-runPreview sync status report without interactive prompts or file modifications

Steps

Purpose:

  • Detect when generated skills/commands have been manually modified
  • Detect when source PRDs have changed (making generated content stale)
  • Offer appropriate actions: regenerate, promote to custom, or keep as-is
  1. Read manifest:

    cat docs/blueprint/manifest.json
    
    • Extract generated.rules section
    • If no generated content, report "Nothing to sync"
  2. Check each generated rule: For each rule in manifest.generated.rules:

    a. Verify file exists:

    test -f .claude/rules/{name}.md
    

    b. Hash current content:

    sha256sum .claude/rules/{name}.md | cut -d' ' -f1
    

    c. Compare hashes:

    • If content_hash matches → status: current
    • If content_hash differs → status: modified

    d. Check source freshness (for rules from PRDs):

    • Hash current PRD content
    • Compare with source_hash in manifest
    • If differs → status: stale
  3. Display sync report:

    Generated Content Sync Status
    
    Rules (.claude/rules/):
    ✅ architecture-patterns.md: Current
    ⚠️ testing-strategies.md: Modified locally
    🔄 implementation-guides.md: Stale (PRDs changed)
    ✅ quality-standards.md: Current
    
    Summary:
    - Current: 3 files
    - Modified: 1 file (user edited)
    - Stale: 1 file (source changed)
    
  4. If --dry-run: Output the sync report from Step 3 and exit. Skip all remaining steps.

  5. For modified content, offer options:

    question: "{name} has been modified locally. What would you like to do?"
    options:
      - label: "Keep modifications"
        description: "Mark as acknowledged, preserve your changes"
      - label: "Discard modifications (regenerate)"
        description: "Overwrite with fresh generation from PRDs"
      - label: "View diff"
        description: "See what changed before deciding"
      - label: "Skip this file"
        description: "Leave as-is for now"
    

    Based on selection:

    • "Keep modifications" → Update content_hash to current, mark as acknowledged
    • "Regenerate" → Regenerate this rule from PRDs
    • "View diff" → Show diff then re-ask
    • "Skip" → Continue to next file
  6. For stale content, offer options:

    question: "{name} is stale (PRDs have changed). What would you like to do?"
    options:
      - label: "Regenerate from PRDs (Recommended)"
        description: "Update with latest patterns from docs/prds/"
      - label: "Keep current version"
        description: "Mark as current without regenerating"
      - label: "View what changed in PRDs"
        description: "See PRD changes before deciding"
      - label: "Skip this file"
        description: "Leave stale for now"
    

    Based on selection:

    • "Regenerate" → Regenerate this rule from PRDs
    • "Keep" → Update source_hash to current, mark as current
    • "View" → Show PRD diff then re-ask
    • "Skip" → Continue to next file
  7. Update manifest after changes:

    • Update content_hash for regenerated files
    • Update source_hash if PRD changes acknowledged
    • Update status field appropriately
  8. Final report:

    Sync Complete
    
    Actions taken:
    - testing-strategies.md: Modifications acknowledged
    - implementation-guides.md: Regenerated from PRDs
    
    Current state:
    - 4 generated rules (all current)
    
    Manifest updated.
    

Tips:

  • Run /blueprint:sync periodically to check for drift
  • Acknowledge modifications you want to keep
  • Regenerating will overwrite local changes
  • Stale content still works, but may miss new patterns from PRDs

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/laurigates/claude-plugins/blueprint-sync">View blueprint-sync on skillZs</a>