How do I install the Check skill?

Run npx skillmds@latest add alexanderop/check-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Check skill do?

Review current changes with parallel subagents It is listed under Productivity on SkillMD.

Is Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

alexanderop (@alexanderop) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Check by alexanderop — Agent Skill

Name: Check
Author: alexanderop

File contents

Code Review

Review current changes using specialized review agents.

Instructions

Step 1: Analyze Changes

Determine review mode:

Uncommitted changes: If <staged_diff> or <unstaged_diff> have content
Branch changes: Otherwise use <branch_diff>

Step 2: Select Reviewers

Based on changed files and diff content, select 2-4 reviewers:

Reviewer	Select When
vue-reviewer	Any `.vue` files
typescript-reviewer	Complex types, generics, type assertions
kcd-test-reviewer	Any `.spec.ts` or `.test.ts` files
accessibility-reviewer	UI elements: buttons, inputs, modals, forms
performance-reviewer	Reactivity patterns, computed/watch, large lists
architecture-reviewer	Cross-feature imports, new feature files
security-reviewer	User input handling, v-html, external data
vueuse-reviewer	Manual event listeners, localStorage, timers
fowler-refactoring-reviewer	Large functions, code duplication

Step 3: Launch Reviewers in Parallel

Launch 2-4 Task tools in a single message with all selected reviewers at once. Each reviewer prompt should include the changed files list and the relevant diff.

Step 4: Compile Report

After all reviewers complete, compile findings into:

# Code Review Report

## Summary
[2-3 sentences]

## Critical Issues
[Must fix - or "None"]

## [Reviewer Name]
[Findings or "No issues"]

## Recommended Actions
1. [Priority actions]

---name: check-2description: Review current changes with parallel subagents---# Code ReviewReview current changes using specialized review agents.<git_status>!`git status`</git_status><current_branch>!`git branch --show-current`</current_branch><merge_base>!`git merge-base main HEAD 2>/dev/null || echo ""`</merge_base><branch_changed_files>!`git diff --name-only main...HEAD 2>/dev/null || echo ""`</branch_changed_files><branch_diff>!`git diff main...HEAD 2>/dev/null || echo ""`</branch_diff><uncommitted_changed_files>!`git diff --name-only HEAD`</uncommitted_changed_files><staged_diff>!`git diff --cached`</staged_diff><unstaged_diff>!`git diff`</unstaged_diff>## Instructions### Step 1: Analyze ChangesDetermine review mode:- **Uncommitted changes**: If `<staged_diff>` or `<unstaged_diff>` have content- **Branch changes**: Otherwise use `<branch_diff>`### Step 2: Select ReviewersBased on changed files and diff content, select 2-4 reviewers:| Reviewer | Select When ||----------|-------------|| vue-reviewer | Any `.vue` files || typescript-reviewer | Complex types, generics, type assertions || kcd-test-reviewer | Any `.spec.ts` or `.test.ts` files || accessibility-reviewer | UI elements: buttons, inputs, modals, forms || performance-reviewer | Reactivity patterns, computed/watch, large lists || architecture-reviewer | Cross-feature imports, new feature files || security-reviewer | User input handling, v-html, external data || vueuse-reviewer | Manual event listeners, localStorage, timers || fowler-refactoring-reviewer | Large functions, code duplication |### Step 3: Launch Reviewers in ParallelLaunch 2-4 Task tools in a **single message** with all selected reviewers at once. Each reviewer prompt should include the changed files list and the relevant diff.### Step 4: Compile ReportAfter all reviewers complete, compile findings into:```markdown# Code Review Report## Summary[2-3 sentences]## Critical Issues[Must fix - or "None"]## [Reviewer Name][Findings or "No issues"]## Recommended Actions1. [Priority actions]```

Frequently asked questions

Check