Skip to content
Skills Library
Programming · Review & audit

check

/check

Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.

Licence
MIT
Last repository change
03.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.

Original author description

Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.

How it works

SKILL.md has no level-two headings · 20 lines, 196 words

SKILL.md preview
---
name: check
description: Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.
---

# Check changes with the crew

Scope: $ARGUMENTS. If no scope is given, check the uncommitted changes in the current repo.

1. **Determine the scope.**
   - Uncommitted work: `git status`, `git diff --stat` and `git diff --staged --stat`.
   - A branch: `git diff <base>...HEAD --stat`.
   - A PR: `gh pr diff <n>`.
   - If there is nothing to check, say so and stop.
2. **Run the tester and the reviewer in parallel.** Both briefs must be self-contained: the repo path, the scope and what the change is meant to do (from the user, the commit messages or the diff).
   - `crew:tester`: add the missing tests for the change, run the suites, and run typecheck/lint or `mvn verify`.
   - `crew:reviewer`: review the production diff.
3. **Report** to the user in their language:
   - **GO / NO-GO**
   - 🔴 blockers and 🟠 should-fix items, with `file:line`
   - the test table from the tester, with the tests it added
   - a suggested commit message, matching the `git log` style
4. Don't fix anything unless the user asks. If they do, route each fix to the right coder (`crew:web-coder`, `crew:plugin-coder` or `crew:ui-builder`), then re-run this check on the fixes only.

Versions

RepositoryScoreLicence
This page · dzusill/claude-crews86MIT
tw93/Waza100MIT
nigelng/nng-kit100MIT
Automatebasics/automatebasics-skills100MIT
tony/skills100MIT
vibiumdev/vibium100Apache-2.0
koda-ai-studio/agent-bom100Apache-2.0
JQ-WCoding/devkit100MIT
ribato22/vibecheck100MIT

Database snapshot: 13.11.2026 · package version ced7fc7d608c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pr-review
    Use when the user asks to review a branch or PR against the base, or asks whether it can be approved or merged ("review this branch", "can I approve this?", "can this be merged?"), including a re-review after new commits. Also for a self-review of the user's own branch before…
  • 100ship
    Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix…
  • 100ship
    Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix…
  • 90review
    Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.
  • 100tester
    Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.
  • 100md-tester
    Use when the user invokes /md-tester to manage test spec markdown files, add or update or delete test entries, process ai|feedback annotations, run integration tests, or fix failing tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.