agentleFS
KUNDURUHIMANEESHREDDYKUNDURUHIMANEESHREDDY/saber/.agents/skills/act-on-feedback/SKILL.md

act-on-feedback

Skill0 starsChanged 57 days agoMITView on GitHub

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the listComments tool to retrieve the user's feedback comments for this session

    line 11
  2. Distinctive:

    If specific feedback comments were attached to this message, act on only those attached comments (match them by their comment id).

    line 12
  3. Very specific:

    When feedback has been tackled, use the resolveComments tool to mark those comments as resolved, or the deleteComments tool to delete them

    line 15
  4. Distinctive:

    Verify your changes are consistent with the rest of the codebase

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Act on Feedback

The user has provided feedback on the current session's changes.

  1. Use the listComments tool to retrieve the user's feedback comments for this session
  2. If specific feedback comments were attached to this message, act on only those attached comments (match them by their comment id); otherwise act on all of the listed comments, or whatever subset the user specified in their message
  3. Understand the intent behind each piece of feedback you are acting on
  4. Make the requested changes to address the feedback
  5. When feedback has been tackled, use the resolveComments tool to mark those comments as resolved, or the deleteComments tool to delete them
  6. Verify your changes are consistent with the rest of the codebase

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.