conflict-detector

Solid

L1-L4 conflict detection between a proposed T4 task and pending-confirm sibling tasks. L1 (file overlap) + L2 (function/region overlap) ship in v3.7.0-beta.2 as deterministic bash. L3 (semantic LLM) + L4 (architectural LLM) are stubbed for v3.7.0-rc.1.

AI & Automation 24 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Conflict Detector **STATUS — v3.7.0-beta.2.** L1+L2 functional; L3+L4 stubbed pending LLM-dispatch infrastructure in rc.1. ## Five conflict types (per spec §21.1) ```toon types[5]{type,definition,detection_layer,cost}: C1,File-level overlap,L1,free C2,Function/region overlap,L2,cheap (~10ms regex) C3,Schema/contract conflict,L2,cheap C4,Semantic intent conflict,L3,LLM (stubbed in beta.2) C5,Architectural conflict,L4,LLM-rare (stubbed in beta.2) ``` ## Layer dispatch (per spec §21.3) ``` ON dispatch_request(task): L1 = check-l1-files.sh ← always run, free IF L1.overlap AND L1.confidence >= 0.95: RETURN conflict(L1) IF L1.overlap (low confidence): L2 = check-l2-syntactic.sh ← drill into overlapping files IF L2.overlap: RETURN conflict(L2) IF task.tier <= 2 OR task.creates_new_pattern: L4 = check-architectural (LLM, stubbed) ← skipped in beta.2 IF L4.contradicts: RETURN conflict(L4) IF task.parent has any pending-confirm sibling: L3 = check-semantic (LLM, stubbed) ← skipped in beta.2 IF L3.contradicts: RETURN conflict(L3) RETURN clear ``` ## Disable Set `AF_CONFLICT_LLM_DISABLED=tru...

Details

Author
nguyenthienthanh
Repository
nguyenthienthanh/aura-frog
Created
8 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

contradiction-resolution

Detects conflicting claims in wiki state (flat memory/ layout), surfaces them via memory/CONFLICTS.md, supports snooze-until-/done, never silent-resolves. User arbitrates every conflict.

2 Updated today
kanadhiayash
AI & Automation Listed

subagent-conflict-detection

Use before dispatching a subagent (especially `isolation:"worktree"`) to avoid three dispatch hazards — file-scope overlap with an in-flight subagent, a stale dispatch base, and collisions with another live agent/session editing the same checkout or git-submodule path. Invoke when about to call the Agent tool with `isolation:"worktree"`; when another subagent is running; right after a merge or branch switch (verify the dispatch base first); or when another Claude session is editing a shared repo/submodule path.

0 Updated today
wei18
AI & Automation Solid

contention-layer

When two skills, agents, or independent research tracks produce conflicting verdicts on the same output, reads the conflict as a signal rather than an error and harvests new skill candidates or insight deltas — including a Dual-Track Grounding conflict (open-frontier track vs internally-grounded recall track disagreeing). Routes skills born from contention to fh-meta (meta-layer), the commons plugin (project-agnostic), or field harvest (domain-specific). Triggered by "two skills conflict", "they produce different conclusions", "contention-layer", "contention harvest", "open vs grounded contradiction", "research tracks disagree".

8 Updated today
chrono-meta