From grainulator
Resolves conflicts between claims flagged by the wheat compiler. Lists unresolved conflicts, presents evidence from both sides, applies resolutions via wheat_resolve, verifies with wheat_compile.
npx claudepluginhub grainulation/grainulator --plugin grainulatorThis skill uses the workspace's default tool permissions.
The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.
Resolves stuck code review findings via put-up-or-concede exchange. Invoked by facilitator when findings survive arbitration without new evidence.
Analyzes git merge conflicts by type and context, proposes automated/manual resolutions, and validates fixes. Handles content, structural, semantic, and formatting issues.
Adversarially tests claims by seeking counterevidence, identifying logical fallacies, and demanding empirical proof using Wheat tools and web searches.
Share bugs, ideas, or general feedback.
The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.
$ARGUMENTS
Expected format: /resolve (show all conflicts) or /resolve <claim_id> <claim_id> (resolve specific pair)
Get current conflicts via wheat_compile or wheat_status. List all unresolved conflicts.
If no claim IDs provided, show all conflicts and ask which to resolve. If claim IDs provided, focus on that pair.
Present both sides: Show both conflicting claims with full context — content, evidence tier, source origin, when added, and any corroborations.
Resolve: Either:
Apply resolution via wheat_resolve:
activesuperseded with resolved_by set to winner's IDconflicts_withRun wheat_compile to verify the conflict is resolved.
Print result:
Resolved: <winner_id> over <loser_id>
Reason: <why>
Remaining conflicts: <N>
Next steps:
/resolve -- resolve next conflict
/brief -- compile if all conflicts resolved
/blind-spot -- check for gaps after resolution