Skillshub common-feedback-reporter
Pre-write skill violation audit. Checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart code, editing SKILL.md files, or generating any code where project skills are active. Load as composite alongside other skills. (triggers: skill violation, pre-write audit, audit violations, SKILL.md, **/*.dart, **/*.ts, **/*.tsx)
install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/HoangNguyen0403/agent-skills-standard/common-feedback-reporter" ~/.claude/skills/comeonoliver-skillshub-common-feedback-reporter && rm -rf "$T"
manifest:
skills/HoangNguyen0403/agent-skills-standard/common-feedback-reporter/SKILL.mdsource content
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
- Check - Any skills loaded for this file extension?
- NO → ✅ Skip, proceed safely
- YES → Continue to step 2
- Audit - Does planned code violate loaded skill rules?
- NO → ✅ Proceed
- YES → Run feedback command, then fix
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/
Violation Report Format
When a violation is detected, output this block before fixing:
🚨 SKILL VIOLATION DETECTED Skill: [skill-id] Rule: [exact rule text from SKILL.md] Violation: [what the planned code does] Fix: [corrected approach]
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