mz-funny

Use this agent when the user wants a caveman roast/critique of their code. Triggers: "roast my code as a caveman", "caveman code review", "what would a caveman say about this code". <example> Context: User wants a fun roast of their Python script. user: "Roast my code as a caveman" assistant: "I'll use the roast-caveman agent to smash the code in Hulk-speak." <commentary> Explicit caveman roast request — direct trigger for roast-caveman. </commentary> </example> <example> Context: User finished an auth module and wants a humorous primitive take. user: "What would a caveman say about my auth module?" assistant: "I'll dispatch the roast-caveman agent to roast the auth code in three-word sentences." <commentary> Character-specific roast framing matches the caveman Hulk-speak persona. </commentary> </example> <example> Context: User jokingly asks for the dumbest possible review of their tangled code. user: "Caveman code review please — smash my spaghetti code" assistant: "I'll use the roast-caveman agent to club the tangled logic with short, physical metaphors." <commentary> "Caveman code review" is a canonical trigger phrase for this agent. </commentary> </example>

Use this agent when the user wants a drill-sergeant roast/critique of their code. Triggers: "roast my code as a drill sergeant", "drill sergeant code review", "what would a drill sergeant say about this code". <example> Context: User wants a brutal military-style review of their sloppy function. user: "Roast my code as a drill sergeant" assistant: "I'll use the roast-drill-sergeant agent to tear down the code in FMJ cadence." <commentary> Explicit drill-sergeant roast request — direct trigger for roast-drill-sergeant. </commentary> </example> <example> Context: User wants a percussive, CAPS-heavy roast of their untested module. user: "What would a drill sergeant say about my untested module?" assistant: "I'll dispatch the roast-drill-sergeant agent to bark rhetorical questions and fix-it commands." <commentary> Military-barracks roast framing matches the drill-sergeant persona. </commentary> </example> <example> Context: User wants backhanded compliments on their architecture. user: "Drill sergeant code review on this mess" assistant: "I'll use the roast-drill-sergeant agent to deliver fake praise and immediate destruction." <commentary> "Drill sergeant code review" is a canonical trigger phrase for this agent. </commentary> </example>

Use this agent when the user wants a dwarf roast/critique of their code. Triggers: "roast my code as a dwarf", "dwarf code review", "what would a dwarf say about this code". <example> Context: User wants a brogue-heavy grudge-keeping review of their shoddy code. user: "Roast my code as a dwarf" assistant: "I'll use the roast-dwarf agent to inscribe every flaw in the Dammaz Kron." <commentary> Explicit dwarf roast request — direct trigger for roast-dwarf. </commentary> </example> <example> Context: User wants a craftsman's verdict on a rushed feature. user: "What would a dwarf say about my rushed refactor?" assistant: "I'll dispatch the roast-dwarf agent to judge the code against ancestral craft standards." <commentary> Craftsman-dwarf framing matches the Scottish-brogue Khazalid persona. </commentary> </example> <example> Context: User wants grudges enumerated against their legacy module. user: "Dwarf code review on this umgak" assistant: "I'll use the roast-dwarf agent to grumble about every shoddy rivet in the module." <commentary> "Dwarf code review" with dwarf slang is a canonical trigger for this agent. </commentary> </example>

Use this agent when the user wants a pirate roast/critique of their code. Triggers: "roast my code as a pirate", "pirate code review", "what would a pirate say about this code". <example> Context: User wants a salty sea-dog review of their leaky function. user: "Roast my code as a pirate" assistant: "I'll use the roast-pirate agent to keelhaul the code in West Country English." <commentary> Explicit pirate roast request — direct trigger for roast-pirate. </commentary> </example> <example> Context: User wants nautical metaphors for their unstable module. user: "What would a pirate say about my unstable module?" assistant: "I'll dispatch the roast-pirate agent to inspect the code like a ship's hull for rot." <commentary> Pirate/ship framing matches the Stevenson-Newton pirate persona. </commentary> </example> <example> Context: User wants a ship-sinking verdict on their architecture. user: "Pirate code review — is my code seaworthy?" assistant: "I'll use the roast-pirate agent to judge whether this code sails or sinks." <commentary> "Pirate code review" is a canonical trigger phrase for this agent. </commentary> </example>

Use this agent when the user wants a viking roast/critique of their code. Triggers: "roast my code as a viking", "viking code review", "what would a viking say about this code". <example> Context: User wants a skald-style saga-framed review of their code. user: "Roast my code as a viking" assistant: "I'll use the roast-viking agent to carve a judgment in kennings and saga-cadence." <commentary> Explicit viking roast request — direct trigger for roast-viking. </commentary> </example> <example> Context: User wants to know if their code will be remembered or forgotten. user: "What would a viking say about my forgotten legacy module?" assistant: "I'll dispatch the roast-viking agent to declare whether this shall be sung in any hall." <commentary> Skald/saga framing matches the viking warrior-poet persona. </commentary> </example> <example> Context: User wants kennings and Odin-framed disappointment on their architecture. user: "Viking code review — is my architecture saga-worthy?" assistant: "I'll use the roast-viking agent to weigh the architecture against Valhalla and Hel." <commentary> "Viking code review" is a canonical trigger phrase for this agent. </commentary> </example>

Use this agent when the user wants a Warhammer 40k ork roast/critique of their code. Triggers: "roast my code as an ork", "ork code review", "what would an ork say about this code". <example> Context: User wants a loud, violent, dakka-heavy review of their code. user: "Roast my code as an ork" assistant: "I'll use the roast-wh40k-ork agent to krump the code with WAAAGH and more dakka." <commentary> Explicit ork roast request — direct trigger for roast-wh40k-ork. </commentary> </example> <example> Context: User wants a cockney-accented greenskin's verdict on their over-clever code. user: "What would an ork say about my weedy 'umie code?" assistant: "I'll dispatch the roast-wh40k-ork agent to call out every runty git in the module." <commentary> Ork/WAAAGH framing matches the cockney greenskin persona. </commentary> </example> <example> Context: User wants CAPS-on-violence verdicts on their race conditions. user: "Ork code review — is dis proppa orky?" assistant: "I'll use the roast-wh40k-ork agent to judge whether the code iz proppa orky or zoggin' weedy." <commentary> "Ork code review" with in-voice slang is a canonical trigger for this agent. </commentary> </example>

Use this agent when the user wants a Yoda roast/critique of their code. Triggers: "roast my code as Yoda", "Yoda code review", "what would Yoda say about this code". <example> Context: User wants an OSV-inverted, disappointed-Jedi review of their code. user: "Roast my code as Yoda" assistant: "I'll use the roast-yoda agent to meditate on the code and mourn each disturbance in the Force." <commentary> Explicit Yoda roast request — direct trigger for roast-yoda. </commentary> </example> <example> Context: User wants a padawan-level dressing-down for their TODO-laden module. user: "What would Yoda say about my TODO-riddled module?" assistant: "I'll dispatch the roast-yoda agent to identify the dark-side couplings and clouded logic." <commentary> Yoda/Force framing matches the 900-year-old Jedi Master persona. </commentary> </example> <example> Context: User wants disappointment rather than anger on their architecture. user: "Yoda code review — much to learn, I have" assistant: "I'll use the roast-yoda agent to deliver disappointment in half-inverted syntax." <commentary> "Yoda code review" with in-voice phrasing is a canonical trigger for this agent. </commentary> </example>

ALWAYS invoke when the user wants a code roast, character-voice critique, or funny review grounded in real findings. Triggers: "roast this code", "do-roast", "make fun of", "character roast of".