Predict FIFA World Cup matches, full tournament paths, and champion probabilities through Codex-native subagents that analyze live news, weather, injuries, markets, Polymarket, tactics, and tournament context while updating a real-time web dashboard. Use when asked to forecast World Cup games, predict the full World Cup outlook, compare match forecasts, or show prediction progress live in a browser.
Create AI image-generation prompts and image-generation workflows for torn-paper editorial collage style posters with layered ripped paper, rough typography, stamps, tape, stickers, cutout subjects, photocopy grain, and collectible evidence-board energy. Use when the user asks to generate, redesign, or prompt an Image Generator for this specific torn-paper collage poster style, especially when they provide a theme plus optional reference image, person photo, news/event data, launch data, product/object photo, cultural moment, technology milestone, or mood/style references.
Use for Chinese-language or China-family-context family-doctor-style parenting and child health management: 育儿, 宝宝护理, 科学养育, 生长发育, 喂养, 母乳, 配方奶, 辅食, 睡眠, 湿疹, 过敏观察, 疫苗沟通, 居家观察, 宝宝档案, parenting.md tracking, 看病问诊, 病例归档, 父母焦虑, 家庭协作, visual parenting plans, or dad-focused caregiving. Also use as a safety bridge when a caregiver raises acute child symptoms in a parenting context. Do not use for diagnosis, prescriptions, medication dosing, lab reports, or adult-only health questions.
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
Use when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline claims expedited review or relaxed process. TRIGGER on "emergency change", "hotfix", "prod incident", "major security hole", "must ship today", "hard deadline", "bypass review", or "fast-track this PR" for qualification only. DO NOT TRIGGER for ordinary urgency, soft deadlines, Friday timing, manager pressure, time-zone delay, or review unless emergency status is disputed.
Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested.