well-formed
Review pull request diffs for code smells, style issues, and safety problems before merging.
npx skills add luongnv89/asm --skill well-formed --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Well-formed corpus skill ## When to Use - When the user asks to "review this PR" or "check the diff" - Before merging any change larger than 10 lines ## Prerequisites - A git repository with the target branch checked out - Read access to the files being reviewed ## Instructions 1. Run `git diff main...HEAD` to list files 2. Read each file and check for common smells 3. Emit a markdown report summarising findings ## Example ```bash $ asm eval ./well-formed Overall score: 95/100 ``` ## Acceptance Criteria - Produces a markdown report with sections per file - Flags any use of `eval()` or `exec` as dangerous - Does not modify the working tree ## Edge cases - Empty diffs: emit a short "no changes" note - Binary files: skip and mention the filename in the report ## Safety See `references/safety.md` for error handling rules. Always confirm before writing. Never run destructive commands without a dry-run.
- When to Use
- Prerequisites
- Instructions
- Example
- Acceptance Criteria
- Edge cases
- Safety
asm eval ./well-formed Overall score: 95/100
What does the well-formed skill do?
Review pull request diffs for code smells, style issues, and safety problems before merging.
How do I install it?
Run `npx skills add luongnv89/asm --skill well-formed --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From luongnv89/asm, a repository with 782 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.