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. When a violation is detected and Auto-fixed: YES, also load +common/common-learning-log to record the mistake. (triggers: skill violation, pre-write audit, audit violations, SKILL.md, **/*.dart, **/*.ts, **/*.tsx, +common/common-learning-log)
Best use case
common-feedback-reporter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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. When a violation is detected and Auto-fixed: YES, also load +common/common-learning-log to record the mistake. (triggers: skill violation, pre-write audit, audit violations, SKILL.md, **/*.dart, **/*.ts, **/*.tsx, +common/common-learning-log)
Teams using common-feedback-reporter should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/common-feedback-reporter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How common-feedback-reporter Compares
| Feature / Agent | common-feedback-reporter | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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. When a violation is detected and Auto-fixed: YES, also load +common/common-learning-log to record the mistake. (triggers: skill violation, pre-write audit, audit violations, SKILL.md, **/*.dart, **/*.ts, **/*.tsx, +common/common-learning-log)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 →](references/violation-examples.md) ## 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 Root Cause: [AMBIGUOUS_RULE | MISSING_COVERAGE | OUTDATED_GUIDANCE | COMPETING_RULES | PATTERN_MISMATCH] User Intent: [1 sentence: what the user was trying to achieve] Skill Gap: [1–2 sentences: what change to the SKILL.md would prevent this next time] Co-skills: [other active skill IDs, comma-separated, or 'none'] ``` ### Root Cause Guide | Code | When to use | |------|-------------| | `AMBIGUOUS_RULE` | Rule wording permits multiple interpretations | | `MISSING_COVERAGE` | Common pattern not addressed anywhere in the skill | | `OUTDATED_GUIDANCE` | Skill references a deprecated API or framework version | | `COMPETING_RULES` | Two loaded skills gave contradictory guidance | | `PATTERN_MISMATCH` | AI misread or misapplied an anti-pattern definition | 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 found, proceed silently — do NOT submit a report - **No "shallow report"**: Always populate Root Cause, User Intent, and Skill Gap — these drive improvement
Related Skills
common-observability
Enforce structured JSON logging, OpenTelemetry distributed tracing, and RED metrics across backend services. Use when adding request correlation, setting up tracing spans, defining SLO burn-rate alerts, or instrumenting middleware. (triggers: **/*.service.ts, **/*.handler.ts, **/*.middleware.ts, **/*.interceptor.ts, **/*.go, **/*.java, **/*.kt, **/*.py, logging, tracing, metrics, opentelemetry, observability, slo)
common-mobile-ux-core
Enforce universal mobile UX principles for touch-first interfaces including touch targets, safe areas, and mobile-specific interaction patterns. Use when building mobile screens, handling touch interactions, or validating safe area compliance. (triggers: **/*_page.dart, **/*_screen.dart, **/*_view.dart, **/*.swift, **/*Activity.kt, **/*Screen.tsx, mobile, responsive, SafeArea, touch, gesture, viewport)
common-mobile-animation
Apply motion design principles for mobile apps covering timing curves, transitions, gestures, and performance-conscious animations. Use when implementing screen transitions, gesture-driven interactions, shared-element animations, or optimizing animation frame rates on iOS, Android, or Flutter. (triggers: **/*_page.dart, **/*_screen.dart, **/*.swift, **/*Activity.kt, **/*Screen.tsx, Animation, AnimationController, Animated, MotionLayout, transition, gesture)
common-error-handling
Cross-cutting standards for error design, response shapes, error codes, and boundary placement across API, domain, and infrastructure layers. Use when defining error hierarchies, wrapping exceptions, building standardized error responses, or placing error boundaries in layered architectures. (triggers: **/*.service.ts, **/*.handler.ts, **/*.controller.ts, **/*.go, **/*.java, **/*.kt, **/*.py, error handling, exception, try catch, error boundary, error response, error code, throw)
common-architecture-diagramming
Standards for creating clear, audience-appropriate C4 and UML architecture diagrams with Mermaid. Use when producing system context diagrams, container views, sequence diagrams, or updating ARCHITECTURE.md files. (triggers: ARCHITECTURE.md, **/*.mermaid, **/*.drawio, diagram, architecture, c4, system design, mermaid)
common-architecture-audit
Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes. (triggers: package.json, pubspec.yaml, go.mod, pom.xml, nest-cli.json, architecture audit, code review, tech debt, logic leakage, refactor)
common-api-design
Apply REST API conventions — HTTP semantics, status codes, versioning, pagination, and OpenAPI standards for any framework. Use when designing endpoints, choosing HTTP methods, implementing pagination, or writing OpenAPI specs. (triggers: **/*.controller.ts, **/*.router.ts, **/*.routes.ts, **/routes/**, **/controllers/**, **/handlers/**, rest api, endpoint, http method, status code, versioning, pagination, openapi, api design, api contract)
common-accessibility
Enforce WCAG 2.2 AA compliance with semantic HTML, ARIA roles, keyboard navigation, and color contrast standards for web UIs. Use when building interactive components, adding form labels, fixing focus traps, or auditing a11y compliance. (triggers: **/*.tsx, **/*.jsx, **/*.html, **/*.vue, **/*.component.html, accessibility, a11y, wcag, aria, screen reader, focus, alt text)
common-workflow-writing
Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions. (triggers: .agent/workflows/*.md, SKILL.md, create workflow, write workflow, new skill, new workflow)
common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
common-tdd
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage. (triggers: **/*.test.ts, **/*.spec.ts, **/*_test.go, **/*Test.java, **/*_test.dart, **/*_spec.rb, tdd, unit test, write test, red green refactor, failing test, test coverage)
common-system-design
Enforce separation of concerns, dependency inversion, and resilience patterns across layered and distributed architectures. Use when designing new features, evaluating module boundaries, selecting architectural patterns, or resolving scalability bottlenecks. (triggers: architecture, design, system, scalability, microservice, module boundary, coupling)