backport

Copy development branch tooling and plans to starter-template with dry-run preview.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/matthewdeaves/peertalk --skill backport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backport
Source: https://github.com/matthewdeaves/peertalk/tree/main/.claude/skills/backport
Command: npx skills add https://github.com/matthewdeaves/peertalk --skill backport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the starter-template branch in sync with the latest Claude Code tooling and plans by copying updates from the development branch, reducing drift and manual rework.

Core Features & Use Cases

  • Syncs the latest .claude/, docker/, tools/, scripts/, plan/, and CI workflows from the development branch to starter-template.
  • Resets all plan statuses to OPEN to reinitialize the template for new work phases.
  • Supports a dry-run option to preview changes before applying them.

Quick Start

Run /backport to sync the latest tooling and plans from the development branch into starter-template.

Frequently Asked Questions about backport

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

FAQPage Schema
How do I sync tooling updates to a starter-template branch?

To sync tooling updates to a starter-template branch, run /backport. It copies .claude/, docker/, tools/, scripts/, plan/, and CI workflows from your development branch to prevent configuration drift.

What is the best way to prevent branch drift when updating Claude Code tooling?

Preventing branch drift when updating Claude Code tooling requires synchronizing development updates to your starter-template. This process copies directories like .claude/ and tools/ while resetting plan statuses to OPEN.

Can I preview changes before syncing files to the starter-template?

Yes, you can preview changes before syncing files to the starter-template by using the --dry-run option. This allows you to review tooling and plan updates before applying them to the branch.

Does the backport process reset plan statuses when synchronizing branches?

Yes, the branch synchronization process resets all plan statuses to OPEN. This reinitializes the starter-template for new work phases after copying the latest plans from the development branch.

What directories are included when synchronizing development tooling to a starter branch?

Synchronizing development tooling to a starter branch includes the .claude/, docker/, tools/, scripts/, plan/, and .github/workflows directories. This ensures all mirrored tooling content remains consistent across branches.