Automated summary
Runs a full pre-submit checklist (type check, lint, format, unit and e2e tests, build, design system audit, git status) before a pull request is created.
Strengths
- Walks through seven checks with the exact pnpm monorepo commands, leaving little room for interpretation.
- The design system audit catches forbidden Tailwind patterns (font-bold, bg-white/5, shadow-*, raw clsx) and enforces cn() from @repo/ui.
- Emits a normalized report with a PASS/FAIL line per step and a final "Ready to submit: YES/NO" verdict.
- On failure it demands the failing command, the error message and a suggested fix for each issue.
Limitations
- Commands are hardcoded for the "portal" workspace with pnpm, so they do not transfer as-is to another repository.
- The design system rules and the branch naming convention are project-specific and must be rewritten elsewhere.
- E2E tests require a dev server that is already running; the skill does not start one.
- Because of disable-model-invocation: true the skill must be triggered manually and will not fire on its own from context.
Use it right before opening or updating a pull request in this pnpm monorepo, to confirm everything will pass in CI.
Avoid it on a repo that does not use pnpm, the portal workspace or this design system, since most commands would fail for the wrong reasons.
Security analysis
SafeThe skill provides a static checklist of common validation commands (type-check, lint, format, tests, build) and code-style patterns. It does not contain destructive commands, exfiltration, obfuscation, or unsafe network operations. The commands are standard developer tooling and the skill is marked as non-invocable by the model.
No concerns found
How this analysis is madeExamples
/pr-check — run the full validation before I open the PR for feature/user-settings./pr-check on my current branch and list every failure with the command that failed, the error message and the fix I should apply./pr-check — I touched several components, so make sure the design system audit passes and show me any forbidden Tailwind classes in my changed files.name: pr-check description: Pre-submit validation checklist for PRs disable-model-invocation: true
PR Check Skill
Purpose
Run comprehensive pre-submit validation before creating a pull request.
Checklist
1. Type Check
pnpm --filter portal type-check
- Must pass with no errors
2. Lint Check
pnpm lint
- Must pass with no warnings
3. Format Check
pnpm exec prettier --check "**/*.{ts,tsx,md}"
- If fails, run
pnpm formatto fix
4. Test Suite
# Unit tests
pnpm --filter portal test
# E2E tests (requires dev server)
pnpm test:e2e
5. Design System Audit
Check for forbidden patterns in changed files:
font-bold,font-semibold-> usefont-mediumbg-white/5,border-white/10-> use design tokensshadow-*-> use border for depth- Direct
clsx/tailwind-merge-> usecn()from@repo/ui/lib/utils
6. Build Verification
pnpm --filter portal build
- Must complete without errors
7. Git Status
- No uncommitted changes
- Branch name follows convention (feature/, fix/, chore/*)
Output Format
## PR Check Results
- [ ] Type check: PASS/FAIL
- [ ] Lint: PASS/FAIL
- [ ] Format: PASS/FAIL
- [ ] Tests: PASS/FAIL (X passed, Y failed)
- [ ] Design system: PASS/FAIL (list violations)
- [ ] Build: PASS/FAIL
Ready to submit: YES/NO
If Failures Found
List each failure with:
- Command that failed
- Error message
- Suggested fix
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pr-check-mrwak9kk/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pr-check-mrwak9kk' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pr-check-mrwak9kk/download' --output '.skill-downloads/pr-check-mrwak9kk/SKILL.md.part' && mv '.skill-downloads/pr-check-mrwak9kk/SKILL.md.part' '.skill-downloads/pr-check-mrwak9kk/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pr-check-mrwak9kk/SKILL.md' && test -s '.skill-downloads/pr-check-mrwak9kk/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr-check' && cp -R '.skill-downloads/pr-check-mrwak9kk' '.claude/skills/pr-check'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pr-check-mrwak9kk'openskills read 'pr-check-mrwak9kk'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pr-check-mrwak9kk/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.