Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .claude/skills/review-code/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,8 +119,8 @@ about something missing, such as a test.
| Ready after fixes | Important findings and no Critical ones |
| Ready to merge | Only Minor findings, non-blocking questions, or no findings |

When there are findings, offer to fix them or post them to the pull
request. Do neither unless the developer asks.
When there are findings, end by noting that fixing them or posting them to
the pull request is a separate request. The review itself does neither.

## Customizing

Expand Down
12 changes: 8 additions & 4 deletions .vortex/docs/content/development/ai.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -134,10 +134,14 @@ The review checks the change against 3 sources, in this order:
updates, tests and front-end code.
3. General engineering judgment.

The review skips anything `ahoy lint` already enforces. It sorts findings
into **Critical**, **Important** and **Minor** and points each one at a
file and line. It ends with a verdict: **Ready to merge**, **Ready after
fixes** or **Needs work**.
For a pull request in another repository, the review uses that
repository's rules and skips the checklist.

The review skips anything that `ahoy lint` or another lint command in
`AGENTS.md` already enforces. It sorts findings into **Critical**,
**Important** and **Minor** and points each one at a file and line. It
ends with a verdict: **Ready to merge**, **Ready after fixes** or **Needs
work**. A merged or closed pull request gets follow-ups and no verdict.

### Adapt the review to your team

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -119,8 +119,8 @@ about something missing, such as a test.
| Ready after fixes | Important findings and no Critical ones |
| Ready to merge | Only Minor findings, non-blocking questions, or no findings |

When there are findings, offer to fix them or post them to the pull
request. Do neither unless the developer asks.
When there are findings, end by noting that fixing them or posting them to
the pull request is a separate request. The review itself does neither.

## Customizing

Expand Down
Loading