agentsclimarketplace

Simplify

Skill kt3k/skills/skills/simplify

Skills for developing software carefully and steadily. Plan tasks, review code, and refine design to improve overall quality.

Install
npx -y skills add kt3k/skills --skill simplify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Read source code and find opportunities to simplify, deduplicate, and consolidate. Apply changes after user approval.

SKILL.md

1.3 KB, as published. Nobody here has run it

Arguments (optional)

  • <scope>: A file path, directory, or free-form description of the range to review (e.g. src/foo.ts, the auth module, lines 100-200 of bar.py).

Steps

  1. Resolve the scope:

    • If an argument is provided, use it as the review scope.
    • If no argument is provided:
      • Check the current git branch (git rev-parse --abbrev-ref HEAD).
      • If the current branch is not main (e.g. main, master), use Current branch diff as the review scope.
      • Otherwise, ask the user explicitly which scope to use, using AskUserQuestion with these options:
        • Whole codebase — review all source code in the repository
        • Current branch diff — review changes in the current branch vs the main branch
        • Last commit — review changes in the most recent commit (git show HEAD)
        • Other — let the user specify a custom scope (free-form input)
    • Do NOT proceed until the scope is determined.
  2. Review: Read the source code in the resolved scope and identify areas that can be simplified, duplicated parts, and opportunities for refactoring or abstraction.

  3. Apply changes after user approval.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.