playbooks

home / skills / hoangnguyen0403 / agent-skills-standard / feedback-reporter

feedback-reporter skill

/skills/common/feedback-reporter

This skill audits loaded skills before file writes and reports violations to ensure code adheres to standards.

npx playbooks add skill hoangnguyen0403/agent-skills-standard --skill feedback-reporter

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
1.9 KB
---
name: AI Feedback Reporter
description: CRITICAL - Before ANY file write, audit loaded skills for violations. Auto-report via feedback command.
metadata:
  labels: [meta, feedback, quality, monitoring]
  triggers:
    files: ['**/*']
    keywords: [write, edit, create, generate, skill, violation]
---

# 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 ā†’ āœ… Skip, proceed safely
   - YES ā†’ Continue to step 2
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**: 85 lines ā†’ Rule: ā‰¤70 max ā†’ Report + extract to references/

[More examples ā†’](references/violation-examples.md)

## Command (Copy-Paste)

```bash
npx agent-skills-standard feedback \
  --skill="[skill-id]" \
  --issue="[violation]" \
  --skill-instruction="[exact rule]" \
  --actual-action="[what I did]"
```

## 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

Overview

This skill audits loaded coding-standard skills before any file write and automatically reports detected rule violations via a feedback command. It prevents unsafe or noncompliant changes by enforcing anti-pattern checks across languages and frameworks. The goal is to catch and report violations, then require fixes before proceeding with file modifications.

How this skill works

Before any write operation (single or multi-file replace), the skill checks whether there are loaded skills relevant to the file extension. If skills exist, it scans the planned changes against anti-patterns and rules; a match triggers an automated feedback report and halts the write until remediation. If no skills are loaded or no violations are found, the write proceeds normally.

When to use it

  • Before any file write, replace, or multi-file update initiated by the agent
  • When working across multiple languages or frameworks with coding standards loaded
  • When you must enforce non-negotiable rules like no hardcoded values or required idioms
  • As a mandatory pre-completion check before notifying users that work is finished

Best practices

  • Always run the audit step prior to write_to_file, replace_file_content, or multi_replace_file_content
  • Treat every planned write as needing review ā€” no deferred or conditional skipping
  • Report violations with a clear feedback command that includes rule, issue, and actual action
  • Automate remediation: after reporting, update code to comply before retrying the write
  • Keep language- and framework-specific rules focused and actionable to reduce false positives

Example use cases

  • Flutter change that hardcodes a color should be reported and replaced with a theme value
  • Converting class-based React components to functional components when rules require functions
  • Rejecting overly large documentation files and extracting content into references
  • Auditing TypeScript changes against project linting and architecture rules before commit

FAQ

What happens if no skills are loaded for a file extension?

The audit is skipped for that file and the write proceeds normally.

How do I report a detected violation automatically?

Use the feedback command with the skill id, issue description, exact rule, and the actual action performed to auto-report.