Feedback Reporter

Priority: P0 - Auto-detect skill violations before file writes

🚨 Checkpoint: Before File Writes

Quick check before write_to_file, replace_file_content, multi_replace_file_content:

1. Check - Any skills loaded for this file extension?
   • NO → ✅ Proceed silently
   • YES → Continue to step 2
2. Audit - Does planned code violate loaded skill rules?
   • NO → ✅ Proceed silently — do NOT submit a feedback report
   • YES → Output violation block below, then fix immediately

Detection Flow

Before file write?
├─ Check file extension → Identify loaded skills
├─ Review skill anti-patterns/rules
├─ Code matches anti-pattern?
│  ├─ YES → 🚨 VIOLATION → feedback command
│  └─ NO → ✅ Proceed
└─ No skills loaded → ✅ Proceed

Examples (Quick Reference)

Flutter: color: Colors.blue → Rule: No hardcoded colors → Report + use theme

React: class MyComponent extends... → Rule: Use functions → Report + convert

SKILL.md: 105 lines → Rule: ≤100 lines max → Report + extract to references/

More examples →

Violation Report Format

When a violation is detected, output this block before fixing:

🚨 SKILL VIOLATION DETECTED
Skill:       [skill-id]
File:        [relative/path/to/file.ext]:[line-range]
Rule:        [exact rule text from SKILL.md]
Violation:   [what planned code does — up to 5-line offending snippet]
Fix:         [corrected approach — up to 5-line corrected snippet]
Auto-fixed:  YES / NO
Co-skills:   [other active skill IDs, comma-separated, or 'none']

Then apply the fix immediately — do not wait for user confirmation.

Pre-Completion Check

Before notify_user or task completion:

Did I write code? YES → Did I audit skills? NO → Audit now

Anti-Patterns

• No "I'll check later": Check before writing, not after
• No "minor change skip": Every write needs check
• No "user waiting skip": 10-second check > pattern violation
• No "clean-pass report": If no violation is found, proceed silently — do NOT submit a feedback issue