big-change

Plan major codebase updates by classifying change types and identifying impacted modules.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/mattsp1290/dotfiles --skill big-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: big-change
Source: https://github.com/mattsp1290/dotfiles/tree/main/.claude/skills/big-change
Command: npx skills add https://github.com/mattsp1290/dotfiles --skill big-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists developers and project managers in planning and coordinating large codebase changes, reducing errors and oversights.

Core Features & Use Cases

  • Interactive Change Planning: Guides the user through gathering necessary information for a major project update.
  • Auto-Detection of Change Context: Classifies the change type and identifies affected areas based on user input and codebase analysis.
  • Comprehensive Documentation: Produces detailed Markdown prompts for task execution and review.

Quick Start

Launch the big-change skill within your project directory to initiate the interactive planning process and generate a structured change prompt.

Frequently Asked Questions about big-change

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

FAQPage Schema
How do I plan major codebase changes without missing impacted modules?

Planning major codebase changes requires interactively gathering project information to automatically classify change types and identify impacted modules, producing structured guidance for implementation and review. This approach reduces errors and oversights during significant project modifications.

What is the best way to coordinate large codebase updates across a development team?

Coordinating large codebase updates is best handled through interactive change planning that guides users through gathering necessary information, auto-detecting change context, and generating detailed Markdown prompts for task execution and team review.

How does automated change classification work for complex project modifications?

Automated change classification works by analyzing user input and the existing codebase to detect the change type and identify affected areas, which then structures the comprehensive documentation needed for implementation.

Can I generate structured implementation prompts for major project updates?

Yes, you can generate structured implementation prompts by interactively gathering project information and analyzing the codebase, which produces detailed Markdown documentation for task execution and review.

Does interactive change management work for any size of codebase modification?

Interactive change management is designed for significant codebase modifications where comprehensive planning is necessary. It suits projects large enough to require automated classification of change types and identification of impacted modules to prevent oversights.

When should I use automated planning tools for codebase modifications?

You should use automated planning tools for codebase modifications when the changes are significant enough that manual planning risks errors and oversights, requiring interactive information gathering and impacted module identification to ensure comprehensive documentation.