skills.rest
bolun-ben-ship
bolun-ben-shipCOMMUNITY
Explore all skills by this author →
GitHub

update-everywhere

Detect git session changes and generate a propagation plan for workspace references.

Updated Mar 20, 2026
Search Tags:#automation#git#workflow#claude#skill-management#orchestrator#propagation
One-click install
npx skills add https://github.com/bolun-ben-ship/RightClickAI-seo-workspace --skill update-everywhere
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-everywhere
Source: https://github.com/bolun-ben-ship/RightClickAI-seo-workspace/tree/main/seo-workflow/update-everywhere
Command: npx skills add https://github.com/bolun-ben-ship/RightClickAI-seo-workspace --skill update-everywhere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-session propagation skill. After any working session, detects every file that changed (via git status + diff), classifies each change against the workspace propagation matrix, scans all dependent targets (SKILLS-REFERENCE.md, install.sh, README.md, workspace CLAUDE.md, client-template, all clients/*/CLAUDE.md and command folders, orchestrator SKILL.md files), builds a full before/after update plan, gets explicit approval, then executes every required propagation, runs install.sh, and verifies no stale references remain. Use after any session where skills, commands, orchestrators, output filenames, platform routing, or workspace structure changed.

  • Read git diffs to identify changed files and cross-reference with propagation rules.
  • Build, present, and require explicit approval for a full before/after update plan.
  • Execute necessary propagations (install.sh runs, references updated, and references validated) and verify no stale references remain.
  • Verify propagation targets across SKILLS-REFERENCE.md, seo-workflow/install.sh, CLAUDE.md, orchestrator SKILL.md files, and client CLAUDE.md files to ensure consistency and traceability.

Quick Start

Run the update-everywhere skill to detect session changes, build a propagation plan, and execute all required updates across the workspace.

Frequently Asked Questions about update-everywhere

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

FAQPage Schema
How do I propagate git changes across multiple workspace files after a session?▼

To propagate git changes across workspace files, read git status and diffs to classify changes against a propagation matrix, then generate and execute a precise update plan across SKILL references and CLAUDE files. Explicit approval is required before any file modifications occur.

What is the best way to keep CLAUDE.md and install.sh references consistent after modifying skills?▼

Keeping CLAUDE.md and install.sh references consistent requires scanning all dependent targets like orchestrator SKILL.md files and client templates, building a full before/after update plan, and verifying no stale references remain after execution.

How does git diff classification work for workspace propagation rules?▼

Git diff classification for workspace propagation works by reading session changes, cross-referencing each altered file against the workspace propagation matrix, and mapping those changes to necessary updates across SKILLS-REFERENCE.md and client CLAUDE.md files.

Do I need explicit approval before applying workspace propagation updates?▼

Yes, explicit approval is required before applying workspace propagation updates. The system builds and presents a full before/after update plan detailing all necessary changes across install.sh and CLAUDE workspace files, pausing execution until you approve.

Why do stale references remain in SKILLS-REFERENCE.md after updating orchestrator files?▼

Stale references remain in SKILLS-REFERENCE.md when post-session propagation is incomplete. Scanning all dependent targets, executing the full propagation plan, and running verification checks ensures no stale references are left behind.

Can I automate workspace consistency checks for client CLAUDE.md files and command folders?▼

You can automate workspace consistency checks by detecting session changes via git, classifying them against the propagation matrix, and scanning client CLAUDE.md files and command folders to generate a precise update plan that eliminates stale references.

Related Skills

Explore More Software Engineering Skills→
erclxerclx
2

claude-docs

Synchronize planning documentation and task boards by analyzing git diffs.

Community
Advanced
RogueRopeRogueRope
2

hugo-content-checker

Audit Hugo content directories for broken links, frontmatter gaps, and duplicates.

Official
Intermediate
manastalukdarmanastalukdar
1

session-update

Append timestamped progress, git status, and branch info to a session file.

Community
Basic
klu-devklu-dev
2

google-workspace-ops

Manages Google Drive, Docs, Sheets, and Slides documents and their structures.

Community
Intermediate