← ClaudeAtlas

repo-improvelisted

Improve an existing repository as a whole. Find out what "better" means for this particular repository from its goals and evidence, agree on the full list with the owner once, then apply every improvement in order. It runs the standard's check and move plan, audits structure, documentation, build, tests and CI, security and privacy, dependencies and size, licensing, the profile's own practices and presentation, and hands each topic to repo-setup, code-review, web-improve or docs-review. Use this whenever the user asks to improve, clean up, professionalize, modernize, audit or fix a repository or project, or asks what a repository needs, even when the request is vague, such as "mejora este repo".
SVN11X/skills · ★ 0 · Code & Development · score 72
Install: claude install-skill SVN11X/skills
# repo-improve "Improve this repository" means something different for every repository. Decide what it means here from evidence and from the owner's goals, agree on it, then work in small steps that each leave the repository better and passing its check. ## Ground rules - Talk to the owner in their language. Write repository artifacts in English. - The owner's goals decide what "better" means. Without confirmed goals there is no list: step 1 is mandatory. - One improvement per pull request. Moving or deleting files, changing public URLs and rewriting history are yellow changes: propose them and wait. - Never invent measurements, results or a passing check. ## 1. Understand and confirm, before anything else 1. Read `README.md`, `docs/goals.md`, `AGENTS.md`, `.standard.yml`, the main source files, the recent commits and, if available, the open issues. For a website, also read the page itself: what it says, what the visitor does, step by step. 2. Write an Understanding block in plain words: what the repository is for, who uses it, the main task step by step, how it works (for example where the processing runs), and anything that looked contradictory. Ask the owner to confirm or correct it. Every later decision rests on this, so do not continue until the owner confirms. 3. Interview the owner for whatever is missing or marked `TODO(owner)`: `docs/goals.md` (vision, users, objectives, non-goals, success criteria, priorities, constraints), `DESIGN.md` for the web profile (ide