AgentSkillsCN

Adressing Feedback

回应反馈

SKILL.md

//--- name: Address feedback description: Systematically review feedback items, apply fixes, validate, and mark items as addressed to keep the queue clean. version: 0.1.0 owners: - team: engineering tags: - feedback - triage - maintenance inputs: /ames marked as addressed.


Address feedback

Intent

Continuously reduce feedback backlog by processing items one by one, implementing fixes, validating changes, and marking addressed feedback so it does not appear again.

When to use

  • New feedback files exist in the feedback directory.
  • You need a repeatable workflow to keep the feedback queue clean.
  • A user requests that feedback be addressed “one by one.”

Preconditions

  • Feedback files exist as JSON under the configured directory.
  • A mechanism to mark feedback addressed is available (endpoint, CLI, or file move).

Workflow

  1. Discover feedback files

    • List JSON files in the feedback directory.
    • Exclude the addressed directory and any ignored patterns.
  2. Read and triage

    • Parse each feedback item.
    • Classify as actionable, duplicate/test, or already addressed.
    • Prioritize the most important items
  3. Address actionable items one by one

    • Reproduce the reported behavior if possible.
    • Identify relevant files and functions.
    • Implement a minimal, targeted fix.
    • Add or update tests when appropriate.
  4. Validate

    • Run relevant tests or checks.
    • Confirm the issue no longer occurs.
  5. Mark addressed

    • Set addressed: true and add an addressed_timestamp.
    • Move the file into the addressed directory (or call an API if provided).
  6. Summarize

    • Provide a concise summary of changes.
    • List addressed feedback IDs.

Guidelines

  • Keep fixes small and focused.
  • Avoid unrelated refactors.
  • Prefer adding tests for regressions.
  • Preserve existing UX patterns.
  • Do not delete feedback; archive it as addressed.

Example output

  • Addressed feedback_20260206_195120_939786.json by removing tab navigation flicker.
  • Addressed feedback_20260206_195740_928404.json by preventing click-through during element selection.

Failure modes

  • If feedback is unclear, note what additional details may be needed but make a best effort fix giving existing information.
  • If unable to reproduce, document assumptions and provide a best-effort fix.
  • If fix requires product decisions, or may stomp on other features use a feature flag to allow enabling and disabling of the fix.