inspection-protocol

Enforce post-change verification commands for Gradle and pnpm projects.

Updated Jan 23, 2025

Search Tags:#verification #build #pnpm #gradle #lint #tests #code-change

Ready to run

npx skills add https://github.com/ymkz/demo-monorepo --skill inspection-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inspection-protocol
Source: https://github.com/ymkz/demo-monorepo/tree/main/.agents/skills/inspection-protocol
Command: npx skills add https://github.com/ymkz/demo-monorepo --skill inspection-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code changes, always run verification commands and only then declare completion. This protocol ensures work is not considered finished until all required checks pass.

Gradle projects: run spotlessCheck, test, build, and intTest; pnpm projects: run build, lint, and test; all commands must pass before completion.

Core Features & Use Cases

Enforces a post-change verification workflow for software projects, ensuring checks are executed before signaling completion.
Provides clear guidance for Gradle and pnpm ecosystems on which checks to run.
Improves release safety by requiring all checks to pass before PRs or deployments.

Quick Start

After making code changes, run the recommended verification commands and declare completion only when all checks pass.

Frequently Asked Questions about inspection-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce verification checks before declaring code changes complete?▼

To enforce verification checks before code changes complete, run designated build and test commands and require them to pass. This protocol automates the workflow so work is not considered finished until all specified quality gates succeed.

What verification commands should I run for pnpm projects after code changes?▼

For pnpm projects, the verification commands to run after code changes are build, lint, and test. All three must pass before completion is declared, ensuring code meets required quality gates.

What checks are required for Gradle projects before signaling completion?▼

The checks required for Gradle projects before completion are spotlessCheck, test, build, and intTest. This verification protocol requires all four commands to pass successfully before work is considered finished.

Why run verification steps like lint and tests before merging a pull request?▼

Running verification steps like lint and tests before merging a pull request improves release safety by catching errors early. This protocol ensures PRs proceed only after verified quality gates have passed.

Does this verification protocol work with both Gradle and pnpm ecosystems?▼

Yes, this verification protocol works with both Gradle and pnpm ecosystems. It provides specific checks for each, applying spotlessCheck, test, build, and intTest for Gradle, and build, lint, and test for pnpm.