codebase-update

Update .codebase documentation to reflect recent code changes.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/stravinest/house-hold-account --skill codebase-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-update
Source: https://github.com/stravinest/house-hold-account/tree/main/.claude/skills/codebase-update
Command: npx skills add https://github.com/stravinest/house-hold-account --skill codebase-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates the .codebase documentation to reflect recent code changes.

Core Features & Use Cases

  • Documentation synchronization after feature additions, refactors, or structural changes.
  • Identify affected sections and update corresponding entries to align with the current codebase.
  • Use Case: After implementing a new feature or API change, update the docs to mirror the new behavior and structure.

Quick Start

Update the .codebase docs to reflect the latest code changes, then open a PR with a concise summary of updates.

Frequently Asked Questions about codebase-update

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

FAQPage Schema
How do I keep codebase documentation in sync after refactoring?

To keep codebase documentation in sync after refactoring, update the .codebase docs to reflect recent structural changes. Identify affected sections and update corresponding entries to align with the current codebase, ensuring consistency during development or PR processes.

What is codebase documentation synchronization?

Codebase documentation synchronization is the process of updating .codebase docs to mirror recent feature additions, architecture changes, and refactors. It enforces aligned documentation by identifying affected sections and updating entries to match the current codebase.

Can I update docs as part of my code review and PR process?

Yes, you can update docs as part of your code review and PR process. The skill supports documentation updates during development and PR processes, allowing you to open a PR with a concise summary of the updates made to align docs with code changes.

What's the best way to update CHANGELOG and docs after an API change?

The best way to update CHANGELOG and docs after an API change is to apply documentation synchronization to the .codebase docs. This updates relevant sections to mirror the new behavior and structure, ensuring consistency with the current codebase before opening a PR.

When do I need to update .codebase documentation?

You need to update .codebase documentation after implementing a new feature, executing a refactor, or making structural architecture changes. It applies to any code modifications that require the documentation to mirror the new behavior and structure.