playbook-update

Update RDPI-enabled repositories by fetching upstream and merging managed files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KMakayee/playbook --skill playbook-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-update
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/playbook-update
Command: npx skills add https://github.com/KMakayee/playbook --skill playbook-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates an RDPI-enabled project to the latest playbook version without overwriting team-owned content in CLAUDE.md, reducing drift and preventing partial/incorrect upgrades.

Core Features & Use Cases

  • Fetch and compare versions: Clones the playbook source, detects the latest commit, and decides whether an update is needed based on .playbook-version.
  • Guided managed-file updates: Upgrades playbook-managed files via diffs and confirmation prompts, while skipping unknown/local files to preserve developer work.
  • Partial CLAUDE.md merge (rules only): Merges only the bottom “RDPI Workflow Rules” section from upstream while keeping the top team-owned half untouched.
  • Optional legacy removals (guardrailed): Reads a removals manifest, validates scope strictly, and prompts before deleting any legacy paths.
  • Version tracking: Writes/overwrites .playbook-version so future updates can determine whether you’re already current.

Quick Start

Run /playbook-update to update the managed files and merge the RDPI rules section while preserving your team-owned CLAUDE.md content.

Frequently Asked Questions about playbook-update

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

FAQPage Schema
How do I update the RDPI playbook in my git repository without losing custom content?

To update the RDPI playbook safely, the workflow fetches upstream, diffs managed files, and guides interactive replacements. It merges only the bottom RDPI Workflow Rules section of CLAUDE.md while preserving your top team-owned content.

How does version tracking work for playbook updates in Claude and Codex projects?

Version tracking works by reading and writing a `.playbook-version` file. This file stores the latest commit hash, allowing the update process to determine whether your repository is already current or requires fetching upstream changes.

What is the best way to merge CLAUDE.md rules without overwriting team-owned sections?

The best way to merge CLAUDE.md rules is through a partial merge that targets only the bottom RDPI Workflow Rules section. This approach skips unknown or local files to preserve developer work and keeps the top team-owned half untouched.

Do I need to manually validate legacy file removals during a repository maintenance update?

You do not need to manually validate legacy file removals. The update process reads a removals manifest, strictly validates the deletion scope, and prompts you interactively before deleting any legacy paths to ensure safe repository maintenance.

Can I use playbook-update to upgrade managed files if my repository has local developer modifications?

Yes, you can upgrade managed files even with local modifications. The process upgrades playbook-managed files via diffs and confirmation prompts while strictly skipping unknown or local files to prevent overwriting your active developer work.