Back to guide/Developer Tools

Multi-File Editing

Scopes the change explicitly, lists affected files to prevent runaway edits, and asks for per-file explanations so you can review incrementally.

claude-code-tipsdescribe_changefile_or_module_1file_or_module_2
Edit View
Prompt
I need to {{describe_change}} across my codebase.

Affected areas:
- {{file_or_module_1}}
- {{file_or_module_2}}
- {{file_or_module_3}}

Requirements:
- Keep all existing tests passing
- Follow the naming conventions in CLAUDE.md
- Update any imports that change
- Do NOT modify files outside the listed areas

Make the changes file by file. After each file, briefly explain what changed and why.

Variables to customize

{{describe_change}}{{file_or_module_1}}{{file_or_module_2}}{{file_or_module_3}}

Why this prompt works

Scopes the change explicitly, lists affected files to prevent runaway edits, and asks for per-file explanations so you can review incrementally.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.

Related prompts

Code Review Assistant

Get thorough code reviews with actionable feedback tailored to your language, framework, and standards.

Context-Aware Code Completion

Providing the surrounding code and project context lets the model match existing patterns exactly. The constraint against modifying existing code prevents unwanted side effects.

Inline Code Suggestion

Constraining suggestions to match existing style and scope produces insertions that feel native to the codebase. The 'no explanation' rule mimics real inline completion behavior.

Code Explanation

The audience level parameter adjusts complexity automatically. Requiring a usage example ensures the explanation is practical, not just theoretical.