# Code Review

> Use when retrieving or addressing PR review comments.

- Skill: `tomevault-io/code-review-75` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/code-review-75`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/code-review-75/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/code-review-75

---


# Code Review Workflow

## Quick Start

```bash
make pr-comments
make pr-comments PR=123
make pr-comments FORMAT=json
make pr-comments FORMAT=markdown
```

Resolve comments in priority order, then verify with formatting, focused tests,
and the full lint gate.

## Comment Categories

| Type                   | Response                                           |
| ---------------------- | -------------------------------------------------- |
| Committable suggestion | Apply if correct, then verify                      |
| Bug or regression      | Reproduce and add or update a focused test         |
| Architecture concern   | Use `code-organization` or `complexity-management` |
| Test gap               | Add coverage at the smallest meaningful level      |
| Question               | Answer directly or make the code clearer           |

## Verification

```bash
make format
make lint
```

Add focused suites when comments touch behavior:

```bash
make test-unit-client
make test-e2e
make test-visual
```

## Rules

- Do not apply suggestions blindly; check the surrounding code first.
- Do not lower lint, TypeScript, test, or metrics thresholds to pass review.
- Keep commits grouped by coherent review concern when possible.
- Re-run `make pr-comments` before finishing review work.

## Related Guides

Before applying this skill, confirm the active task against
[../AI-AGENT-GUIDE.md](../AI-AGENT-GUIDE.md) and
[../SKILL-DECISION-GUIDE.md](../SKILL-DECISION-GUIDE.md) so every relevant
skill is consulted.

## Line Length Disclosure

Before presenting changes, check changed text files for lines longer than 100 characters.
If any exist, tell the user each `path:line` and measured character count.
Treat this as disclosure, not failure, unless a project gate fails.

## Supporting Files

- [reference/quality-standards.md](reference/quality-standards.md): review
  evidence, verification commands, and protected quality rules.

---
> Source: [VilnaCRM-Org/crm](https://github.com/VilnaCRM-Org/crm) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-16 -->