Protocol for @feedback annotations in source code. Use when user mentions @feedback, address feedbacks, inline feedback, or when encountering @feedback markers during any task.
From feedbacksnpx claudepluginhub obsfx/cc-feedback --plugin feedbacksThis skill uses the workspace's default tool permissions.
references/comment-patterns.mdGuides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Designs scalable batch/streaming data pipelines, warehouses, lakehouses using Spark, dbt, Airflow, Kafka/Flink, and cloud platforms like Snowflake, BigQuery, Databricks.
Builds production Apache Airflow DAGs using best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch jobs.
@feedback annotations are inline source code comments that describe desired changes. They use the file's native comment style (//, #, --, /* */, <!-- -->).
// @feedback: <desired change>
// @agent-response: <what was done>
The @agent-response line is added directly below the @feedback line using the same comment style after implementing the change.
@feedback with no @agent-response below it@feedback followed by @agent-response on the next line@feedback in source files, exclude non-source dirs@agent-response: <summary> — max 300 characters. If unable: @agent-response: skipped - <reason>When encountering @feedback while working on other tasks: note them to the user and offer to address if related. Do not address silently.
For comment style details and edge cases (multi-line blocks, inline placement, nested comments): see references/comment-patterns.md.