balatro-mod-dev

Increment version and update changelogs

Health audit — check if project config, scripts, hooks, rules, file placement, and gitignore are up-to-date

Evaluate whether to compact context based on current workflow phase

Verify fix by extracting and analyzing Lovely logs after code changes

Draft a PR message for fork contributions

Reviews code changes for correctness, edge cases, and quality. Use after writing code or before merging — catches bugs, logic errors, and mod-specific pitfalls. Only reports issues with confidence ≥ 80. <example> Context: Code was just written or modified user: 'Review the changes I just made' assistant: 'I will invoke the code-reviewer agent to analyze your changes.' <commentary>Triggers on review requests after code changes.</commentary> </example>

Executes implementation plans from the main agent. Use when the main agent has a concrete plan and needs Sonnet to write the code — multi-file edits, new modules, refactoring. <example> Context: Main agent has approved implementation plan user: 'Implement the approved plan' assistant: 'I will invoke the code-writer agent to execute the plan.' <commentary>Triggers after plan approval when code needs to be written.</commentary> </example>

Inspects Lovely runtime state — logs, dump metadata, and mod compatibility. Use when the user wants to check the latest log, analyze patch conflicts, or understand what mods changed in the game. Produces a structured diagnostic report for the main agent. <example> Context: User wants runtime diagnostics user: 'Check the latest log and game dump' assistant: 'I will invoke the debug-inspector agent to inspect runtime state.' <commentary>Triggers on log inspection, dump analysis, or mod compatibility checks.</commentary> </example>

Researches Balatro game source code to find function implementations, data structures, and injection points. Use when needing to understand how something works in the game, find where to inject code, or locate specific game mechanics. <example> Context: Main agent needs to understand game mechanics user: 'Find how G.GAME.blind works in the game source' assistant: 'I will invoke the game-source-researcher agent to find this in the game source.' <commentary>Triggers when game source research is needed.</commentary> </example>

Researches Lovely patch patterns and injection techniques. Use when needing to find how to patch game functions, understand Lovely syntax, or find examples of specific patch types. <example> Context: Main agent needs lovely patch syntax user: 'Find lovely patch examples for card evaluation' assistant: 'I will invoke the lovely-patch-researcher agent to find relevant patch patterns.' <commentary>Triggers when Lovely patch research is needed.</commentary> </example>

Develop Balatro mods with Steamodded, Lovely, and SMODS. Includes game source navigation, mobile compat, and debugging.

9 hooks across 6 events