update-refs

Propagate terminology renames across code, documentation, and site content.

1.8k|153|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/maxritter/claude-pilot --skill update-refs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-refs
Source: https://github.com/maxritter/claude-pilot/tree/main/.claude/skills/update-refs
Command: npx skills add https://github.com/maxritter/claude-pilot --skill update-refs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes terminology across the Claude Pilot repository by updating names and descriptions wherever they appear.

Core Features & Use Cases

  • Terminology sync: propagate naming updates across commands, skills, workflows, and UI text.
  • Documentation alignment: ensure references in README, docs site, and help texts stay in sync with current terminology.
  • Audit & rename: identify legacy terms and apply consistent updates across code and docs.

Quick Start

Use the update-refs skill to apply a renamed feature across code and documentation.

Frequently Asked Questions about update-refs

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

FAQPage Schema
How do I propagate a codebase rename across documentation and UI text?

You propagate renames by applying a renamed feature across code and documentation, ensuring references in README, docs site, and help texts stay in sync with current terminology to maintain cross-file consistency.

What is terminology standardization in a software repository?

Terminology standardization in a software repository updates names and descriptions wherever they appear across code, documentation, and site content to enforce consistency and eliminate legacy terms.

How do I sync documentation references after renaming a feature?

You sync documentation references by applying terminology updates across README files, documentation sites, and help texts, ensuring all references match the current naming conventions across the codebase.

Can I update terminology across commands, skills, and workflows simultaneously?

Yes, you can update terminology across commands, skills, and workflows simultaneously, as the process handles renames and applies consistent updates across code, documentation, and site content in one pass.

What's the best way to audit and identify legacy terms in a codebase?

The best way to audit and identify legacy terms is to trigger a terminology sync, which identifies outdated references and applies consistent updates across code, documentation, and UI text automatically.

Does renaming a feature require manually updating help texts and README files?

No, renaming a feature does not require manually updating help texts and README files, as the process enforces automated propagation of terminology changes across all documentation and site content.