Project Validation

Use after code changes to choose and run validation commands for Node, JavaScript, TypeScript, Python, Go, Dart, Java, Kotlin, C++, Swift, or Objective-C projects. Prefer project-defined commands and report skipped checks and risks.

559 stars 13 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add KunoLu/640-skills --skill project-validation
Manual install
git clone --depth 1 https://github.com/KunoLu/640-skills.git /tmp/640-skills
mkdir -p ~/.claude/skills
cp -r /tmp/640-skills/sbtd-workflow-onboard/templates/skills/project-validation ~/.claude/skills/project-validation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Project Validation Skill

Use this Skill after code changes.

## General Rules

- Prefer commands already defined by the project.
- When `rtk` is available, prefer `rtk` for non-reporting commands; for unit tests, API / integration tests, Playwright Web E2E, Maestro Mobile / Hybrid E2E, or any command that must generate report files, first apply the `rtk` and reporting-test Gate.
- Do not bypass project configuration.
- Do not modify lock files unless required by the task.
- If full checks are expensive, run focused checks first.
- State which checks were skipped and the remaining risks.

## `rtk` and Reporting-Test Gate

`rtk` is a command-output compression layer, not a test runner. Before executing validation commands, first distinguish between “only terminal facts are needed” and “file side effects must be produced.”

- lint, typecheck, static analysis, build, read-only checks, or diagnostic commands that do not depend on persisted reports can generally prefer `rtk`.
- If unit tests, API / integration tests, Playwright Web E2E, Maestro Mobile / Hybrid E2E, Flutter / Xcode / Gradle / Maven, or similar test commands need to retain coverage, JUnit, HTML, JSON, trace, raw report, or Markdown summaries in the current run, use the project-native command by default, or a no-cache / report-safe command explicitly provided by the project.
Read the full skill on GitHub

Details

Skill name
project-validation
Path
sbtd-workflow-onboard/templates/skills/project-validation/SKILL.md
License
Apache-2.0
Repo updated
13 November 2026

FAQ

What does the Project Validation skill do?

Use after code changes to choose and run validation commands for Node, JavaScript, TypeScript, Python, Go, Dart, Java, Kotlin, C++, Swift, or Objective-C projects. Prefer project-defined commands and report skipped checks and risks.

How do I install the Project Validation skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add KunoLu/640-skills --skill project-validation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Project Validation popular?

It lives in KunoLu/640-skills, which has 559 GitHub stars and 13 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.