hashgraph-online/awesome-codex-plugins / plugins/beastlabai/multi-llm-plugin/skills/multi-llm
multi-llm
FlaggedOrchestrate plan reviews, task generation, implementation and code reviews across several LLM CLIs in parallel, or ask every model one free-text question about a plan. Use when the user says: review my plan, multi-llm, run a code review, generate tasks from a plan, implement this plan, ask the models about my plan.
schemas/code_review_issues.schema.json
View on GitHub{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Code Review Issues",
"type": "array",
"items": {
"type": "object",
"required": ["title", "desc", "importance", "file", "type"],
"properties": {
"title": { "type": "string" },
"desc": { "type": "string" },
"importance": { "type": "string", "enum": ["high", "medium", "low"] },
"file": { "type": "string" },
"line_range": {
"type": ["array", "null"],
"items": { "type": "integer" },
"minItems": 2,
"maxItems": 2
},
"type": {
"type": "string",
"enum": ["bug", "missing", "improvement", "style", "scope"]
},
"anchor_text": { "type": "string" },
"introduced_by": {
"type": ["string", "null"],
"description": "Commit reviews only: the short SHA of the commit that introduced the issue, as the prompt's commit list shows it (the merge for code a merge brought in), or null. A claim the plugin checks against the range and git blame (plans/review-commits.md §2.6)."
},
"scope_relation": {
"description": "Optional: the reviewer's provisional scope classification of the issue's proposed action, \"in_scope\" | \"scope_extension\" | \"unclear\" (plans/scope-policy-and-report-tags.md §3). Deliberately untyped: a missing or malformed value reads \"unclear\" (utils/scope_policy.normalize_scope_fields) and never discards the issue."
},
"scope_reason": {
"description": "Optional: one short line saying why, against the scope baseline."
},
"scope_reference": {
"description": "Optional: the baseline section or text the classification rests on, or \"\"."
},
"suggested_fix": {
"type": "object",
"properties": {
"format": { "type": "string", "enum": ["unified_diff", "before_after"] },
"before": { "type": "string" },
"after": { "type": "string" },
"diff": { "type": "string" }
}
}
}
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |