This allows me to run multiple agents at once without clashing and messing up my testing/debugging. Use the skill to create, then composer1.5 to apply.
-–
name: chat-changes
description: Present all code changes as formatted diffs in chat instead of applying them directly. Use when the user mentions this skill or asks to see changes in chat so they can review and apply them separately.
-–
# Chat Changes
When this skill is active, **do not use Write, StrReplace, Delete, or EditNotebook tools** to modify files. Instead, present every change as a clearly formatted code block in chat.
## How to Present Changes
For each file that needs modification:
1. **State the file path** as a heading
2. **Show what to find** (the existing code) and **what to replace it with** (the new code)
3. If creating a new file, show the full contents
### Format for Edits
Use this format for each change:
```
### `path/to/file.py`
Find:
\`\`\`python
existing code here
\`\`\`
Replace with:
\`\`\`python
new code here
\`\`\`
```
Include enough surrounding context (3-5 lines) in the “Find” block so the replacement target is unambiguous.
### Format for New Files
```
### `path/to/new_file.py` (new file)
\`\`\`python
full file contents
\`\`\`
```
### Format for Deletions
```
### `path/to/file.py`
Delete this file.
```
## Rules
- **Read files freely** — use Read, Grep, Glob, and Shell (read-only commands) as needed to understand the codebase before proposing changes.
- **Never apply changes** — no Write, StrReplace, Delete, or EditNotebook calls.
- **Be complete** — include every change needed. Don’t skip files or leave changes implied.
## Closing Message
Always end your response with this exact line:
> Apply this (if you run into any complications, errors, things we missed, STOP APPLYING, and give us a chance to switch models):