// Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
| name | simplify |
| description | Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality. |
Review changes in the current branch, or in the state the user specifies. Apply these criteria without changing behavior:
Names: Shorten verbose names while keeping them clear. Prefer human-readable concepts (baseline) over compound phrases that are more mechanical / academic (lastObservedDiskContent).
Combine related concepts: If two types, functions, or constants overlap significantly, merge them. The fewer distinct concepts a reader must hold in their head, the better. Example: two union types sharing 3 of 4 values → one type with shorter value names.
Derivability: If a value can be computed from other values already in scope, don't pass or store it separately. Removing derivable state often simplifies signatures, types, and control flow in one move. Example: an isDirty parameter that's always derived from computing editorContent !== baseline can be dropped.
Scope: Only touch code in the specified scope. Validate your work does not break existing functionality.
When we finish a feature. Use when the user says work is done, asks to merge a worktree back to main/master, or clean up a worktree.
Create clean, subtitle-ready `.srt` subtitles for a local audio or video file using Whisper CLI. Use this when the user asks to transcribe a local media file, generate subtitles, create captions, or make an `.srt` for a specific local file path.
Write concise alt text for a local image file. Use this when the user asks for alt text, accessibility text, or a brief image description for a specific local image path. Pass the target image path as `$0`.