{"name":"claude-code-skill","title":"Claude Code skill template","description":"A Claude Code skill template with a SKILL.md example and a supporting file, plus the frontmatter fields, scopes and two variants explained.","category":"agents","updated":"2026-11-08","url":"https://sniptide.com/templates/claude-code-skill","files":[{"name":".claude/skills/review-pr/SKILL.md","language":"markdown","content":"---\nname: review-pr\ndescription: Review the current branch or a pull request against this project's checklist. Use when asked to review changes, check a PR or look over a diff before merging.\n---\n\n# Review a pull request\n\nReview the changes against the main branch and report problems, ordered by how much they matter.\n\n## Steps\n\n1. Read the diff: `git diff main...HEAD`. For a pull request number, run `gh pr diff <number>`.\n2. Read each changed file in full where the diff alone doesn't show the context.\n3. Run the checks: `pnpm lint && pnpm typecheck && pnpm test`.\n4. Go through [checklist.md](checklist.md) for every changed file.\n5. Report your findings in the format below.\n\n## Report format\n\nFor each finding, give the file and line, what is wrong, and a concrete fix:\n\n- **Blocking**: bugs, security problems, failing checks, missing tests for new behavior.\n- **Should fix**: unclear names, duplicated code, missing error handling.\n- **Optional**: style and small improvements.\n\nEnd with one line: ready to merge, or the number of blocking findings.\nDon't change any code during a review unless asked to.\n"},{"name":".claude/skills/review-pr/checklist.md","language":"markdown","content":"# Review checklist\n\n## Correctness\n\n- Does the code do what the pull request says, including empty, missing and very large inputs?\n- Are errors handled where they happen, with a message a person can act on?\n- Do new database queries use an index, and do migrations run on a table with data in it?\n\n## Tests\n\n- Is every change in behavior covered by a test that fails without it?\n- Do tests check results rather than implementation details?\n\n## Security\n\n- Is all user input validated before use?\n- Do new routes check that the user is signed in and allowed to see the data?\n- Are secrets read from the environment, never written in code or logs?\n\n## Readability\n\n- Do names say what things are? Would a new teammate follow the code without the PR description?\n- Is there dead code, a leftover `console.log` or a commented-out block?\n"}]}