Reviews git diffs against standards, spec, and code contracts using parallel sub-agents.
npx skills add https://github.com/Yassimba/loom --skill code-review-yassimba
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/Yassimba/loom/tree/main/skills/code-review Command: npx skills add https://github.com/Yassimba/loom --skill code-review-yassimba
@cc or CONTRACTS obligations, verifies the change complies with them. - Use Case: Before merging a feature branch, ask for a review since main. The Skill pins the fixed point, locates the spec and standards files, spawns parallel review sub-agents, and reports findings side by side under separate headings. ## Quick Start Use the code-review skill to review all changes on this branch since main against our coding standards and the originating spec.High-intent search queries and answers about installing and using this skill.
Provide a fixed point such as a commit SHA, tag, branch name, or HEAD~5, and the Skill diffs it against HEAD using a three-dot git diff. If you don't specify one, it asks before proceeding and fails early on bad refs or empty diffs.
The Spec axis locates the originating spec from issue references in commit messages, a user-provided path, or spec files under ai-docs/, specs/, or .scratch/. A sub-agent then reports missing requirements, scope creep, and incorrect implementations with quoted spec lines.
It uses any documented repo standards such as CODING_STANDARDS.md or CONTRIBUTING.md, plus a built-in baseline of Fowler code smells like Duplicated Code and Feature Envy. Documented repo standards always override the baseline, and smells are reported as judgement calls.
Yes, when the repository contains production @cc declarations or CONTRACTS files, a Code Contracts axis is enabled. A dedicated sub-agent runs the code-contracts verify procedure against the diff and reports violations with contract IDs and evidence.
Standards, Spec, and Code Contracts answer different questions, so a change can pass one axis and fail another. Keeping reports separate prevents one axis from masking failures in another, and findings are never merged or reranked across axes.
danielsuguimotoImplements ticket requirements on an existing feature branch or master with validated code targets.
badbsallyyRebase a GitHub pull request onto main and run automated checks.
arndvsAudits changed files, diffs, and stack tooling before opening a pull request.
damoke012Reviews a git diff against coding standards and the originating spec in parallel sub-agents.