From 657c953e3f8faab6e01741caa8c2e20196cab48f Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 21 Jan 2026 14:48:39 -0700 Subject: [PATCH] docs(list): alphabetise skills --- README.md | 36 ++++++++--------- skills/addressing-agent-comments/SKILL.md | 47 +++++++++++++++++++++++ 2 files changed, 65 insertions(+), 18 deletions(-) create mode 100644 skills/addressing-agent-comments/SKILL.md diff --git a/README.md b/README.md index c03c41c73fc2159ea7786b5e6a1f78811bfa4868..b180aef0d541af18af0a8f4bd73f46dab41f3fc9 100644 --- a/README.md +++ b/README.md @@ -19,9 +19,22 @@ Refer to [§ Token stats](#token-stats) for a detailed breakdown of each skill's well-structured Agent Skills following best practices. Use when writing new skills, reviewing existing skills, or when the user mentions skill authoring. +- [creating-tasks-through-lunatask](skills/creating-tasks-through-lunatask/SKILL.md): + Creates tasks in Lunatask for todos, reminders, deferred work, and + handoffs. - [formatting-commits](skills/formatting-commits/SKILL.md): Creates commits strictly following Conventional Commits format via the `formatted-commit` CLI. +- [frontend-accessibility](skills/frontend-accessibility/SKILL.md): + Generates accessible HTML, React, and frontend code following WCAG 2.2 + AA guidelines. Focuses on semantic HTML, keyboard accessibility, and + screen reader compatibility. +- [handling-customer-data](skills/handling-customer-data/SKILL.md): + Handles customer data responsibly by answering questions about data + without ever seeing the data directly. +- [humanizer](skills/humanizer/SKILL.md): removes signs of AI-generated writing + from text, making it sound more natural and human (initially copied from + [blader/humanizer] then customised) - [invoking-subagents](skills/invoking-subagents/SKILL.md): Invokes ad-hoc subagents to read through lots of data and extract relevant information. Useful for exploring repositories, reading git logs, @@ -32,33 +45,20 @@ Refer to [§ Token stats](#token-stats) for a detailed breakdown of each skill's - [querying-documentation](skills/querying-documentation/SKILL.md): Spawns focused agents to search specific language/framework documentation and answer moderately complex queries. -- [creating-tasks-through-lunatask](skills/creating-tasks-through-lunatask/SKILL.md): - Creates tasks in Lunatask for todos, reminders, deferred work, and - handoffs. - [resuming-work-through-lunatask](skills/resuming-work-through-lunatask/SKILL.md): Resumes previously deferred work from Lunatask. Use when user pastes a task note, shares a deep link, or references continuing earlier work. -- [frontend-accessibility](skills/frontend-accessibility/SKILL.md): - Generates accessible HTML, React, and frontend code following WCAG 2.2 - AA guidelines. Focuses on semantic HTML, keyboard accessibility, and - screen reader compatibility. -- [handling-customer-data](skills/handling-customer-data/SKILL.md): - Handles customer data responsibly by answering questions about data - without ever seeing the data directly. -- [humanizer](skills/humanizer/SKILL.md): removes signs of AI-generated writing - from text, making it sound more natural and human (initially copied from - [blader/humanizer] then customised) +- [resolving-secrets](skills/resolving-secrets/SKILL.md): Wraps shell + commands to resolve secret references in environment variables. +- [reviewing-code](skills/reviewing-code/SKILL.md): Reviews code for + correctness, security, reliability, performance, and quality. Use when + asked to review code, a PR, a diff, or changes. - [scripting-with-go](skills/scripting-with-go/SKILL.md): Creates executable Go scripts with shebang-like behavior for long-lived automation. - [writing-roc-lang](skills/writing-roc-lang/SKILL.md): Writes Roc code with strong static types, helpful compiler errors, and functional programming. Covers both full applications and one-off scripts. -- [resolving-secrets](skills/resolving-secrets/SKILL.md): Wraps shell - commands to resolve secret references in environment variables. -- [reviewing-code](skills/reviewing-code/SKILL.md): Reviews code for - correctness, security, reliability, performance, and quality. Use when - asked to review code, a PR, a diff, or changes. [blader/humanizer]: https://github.com/blader/humanizer diff --git a/skills/addressing-agent-comments/SKILL.md b/skills/addressing-agent-comments/SKILL.md new file mode 100644 index 0000000000000000000000000000000000000000..8d876aaa945b7002314776425aa6778dd06f150e --- /dev/null +++ b/skills/addressing-agent-comments/SKILL.md @@ -0,0 +1,47 @@ +--- +name: addressing-agent-comments +description: Finds AGENT comments in code, gathers feedback, and carries out requested changes. Use when scanning a repo for inline agent notes, decision requests, or tooling tags. +metadata: + source: https://github.com/ampcode/amp-contrib +--- + +Search for inline `AGENT:` comments, read the surrounding code, and follow through on the request. + +## When to use + +- You need to collect and resolve inline agent notes or change requests +- A repo uses a tag like AGENT: to point at work items +- You are asked to scan for inline feedback embedded in code + +## Search process + +1. Identify the instruction tag for the repo. Default to `AGENT:` if none is provided. +2. Use ripgrep to find the tag with context: + +```bash +rg -n --fixed-strings "AGENT:" -C 3 +``` + +3. If multiple tags are used, repeat the search for each tag. + +## Review process + +- Read each comment with surrounding code to understand scope and intent +- Make the change or address the concern where feasible +- If a request is unclear, document assumptions and raise questions +- Update or remove resolved AGENT: comments + +## Output format + +- Group findings by file path +- Include line numbers and relevant context for each comment +- Summarize key themes and action items at the end + +## Expected actions + +After finding AGENT: comments: + +1. Analyze the request in each comment +2. Make the change, or explain why you did not +3. Resolve or update the instruction comment +4. Provide a brief summary of actions taken and any open questions