cr
Check the branch marks its generated files, review it with /code-review at high, then answer the findings with /code-review-response.
SKILL.md.claude/skills/cr/SKILL.md
GitHubCode Review and Response
- Check that the branch marks what it generates, so the review reads sources
alone. Among the files
scripts/changed-sources.shlists, find each one a script, a generator or amisetask writes. Mark it in.gitattributes(linguist-generated=true -diff) and in.coderabbit.yaml'spath_filters, by a glob where its siblings are generated too. Then runmise run check-review-filters, which holds the two files to each other, and commit the marks. - Invoke the
code-reviewskill withhigh, overorigin/main...HEAD: once the branch is pushed its upstream diff is empty, and a stale localmainpulls in merged work. - Answer its findings with the
code-review-responseskill. With no findings, invoke/distillalone: the response would have ended with it.