Skip to content
cccskills
FreePublished on GitHub

improve-add-skill

Improve the repo-local add skill from reviewed Neovim plugin categorization corrections. Use when a correction commit, PR review result, diff, or artifact such as a `teach:` commit shows that `$add` placed, excluded, or reasoned about plugins incorrectly and the reusable lesson should be folded back into `.codex/skills/add/**`.

The English summary is being prepared. Showing the original description.

yutkat/my-neovim-pluginlist833 stars(GitHub 833 + cccskills 0)

Run score Not tested

See how to install

Files included (2)

  • SKILL.md2.0 KB
  • agents/openai.yaml216 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Improve Add Skill

Overview

Turn reviewed corrections from $add PRs into small, reusable improvements to the add skill.

Workflow

  1. Read the correction artifacts named in the user request, such as a commit diff, PR body, .reason.md, review comment, or /tmp/add-skill-feedback.md.
  2. Read .codex/skills/add/SKILL.md, .codex/skills/add/references/PLACEMENT_RULES.md, and .codex/skills/add/references/SECTION.md.
  3. Identify only the actual reviewed correction: moved plugin entries, removed entries, changed .reason.md categories, or explicit rationale in the commit message.
  4. Convert the correction into the smallest reusable rule that would have prevented the mistake.
  5. Edit only .codex/skills/add/SKILL.md and .codex/skills/add/references/*.md.

Prefer references/PLACEMENT_RULES.md for categorization lessons. Update SKILL.md only when the workflow itself needs to change.

Generalization Rules

  • Generalize from plugin purpose and user workflow, not from a single repository name.
  • Keep a repository-specific rule only when the correction is about an exclusion or a uniquely named ecosystem with no broader lesson.
  • Do not add a rule when the diff is only formatting, ordering, typo repair, badge repair, or a one-off judgment with unclear rationale.
  • Do not change the plugin list markdown files, .reason.md, workflows, dependencies, or generated files.

Output

  • Keep changes minimal and easy to review.
  • Preserve existing wording style in the target file.
  • Report the correction source, the rule added or changed, and any artifact that was too ambiguous to use.

If the correction cannot be generalized safely, make no file edits and explain why.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add

Free

Categorize new Neovim plugins and insert them into the correct markdown category files

The English summary is being prepared. Showing the original description.

yutkat/my-neovim-pluginlist833Updated Oct 26, 2026

unarchive

Free

Restore unarchived Neovim plugins from Archived.md to existing categories using commit history. Use when processing archive-check results or restoring previously archived plugin entries.

The English summary is being prepared. Showing the original description.

yutkat/my-neovim-pluginlist833Updated Oct 26, 2026

write-teach-commit

Free

Draft `teach:` commit messages for `.github/workflows/improve-add-skill.yml`. Use when preparing or reviewing a correction commit that should trigger the Improve Add Skill workflow from `$add` categorization feedback, including moved plugin entries, removed or excluded plugins, changed `.reason.md` categories, or review-approved rationale that should be generalized into `.codex/skills/add/**`.

The English summary is being prepared. Showing the original description.

yutkat/my-neovim-pluginlist833Updated Oct 26, 2026

See all skills by yutkat

Report a problem with this skill