skills.rest
Abildtoft
AbildtoftCOMMUNITY
Explore all skills by this author →
GitHub

kramme:verify

Run formatting, linting, type-checking, builds, and tests on affected code.

2|2|Updated Jan 15, 2026
Search Tags:#linting#formatting#build#code-quality#verify#tests#type-check
One-click install
npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kramme:verify
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Averify
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure code quality and project health by running verification checks (formatting, linting, type checking, builds, and tests) on affected code based on the project's configuration.

Core Features & Use Cases

  • Automated Verification: Run formatting, linting, type checking, builds, and tests on changed code.
  • Context-Aware: Reads CLAUDE.md for commands and config; falls back to CI configs or project files when missing.
  • Use Case: When preparing a PR, run verification to catch issues early across multiple targets.

Quick Start

Trigger the verify skill to check the current repository for formatting, linting, type checking, and test failures and report results.

Frequently Asked Questions about kramme:verify

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

FAQPage Schema
How do I automate code verification for formatting, linting, and tests before merging a PR?▼

Automating code verification involves running a suite of checks against affected code to catch issues before merging. This process detects formatting, linting, type-checking, builds, and tests to validate code quality across multi-project repositories and CI pipelines.

What is the best way to run formatting and type-checking on affected code in a multi-project repository?▼

Running checks on affected code in a multi-project repository requires determining the base branch and discovering Nx targets if present. This Skill reads CLAUDE.md for commands and falls back to CI configs or project files to execute the checks.

How does code verification detect which linting and build commands to run?▼

Code verification detects commands by reading CLAUDE.md for configuration. When CLAUDE.md is missing, it falls back to parsing existing CI configs or project files to identify the appropriate formatting, linting, type-checking, and build commands.

Can I use automated code verification in CI pipelines for multi-project repositories?▼

Yes, you can use automated code verification in CI pipelines for multi-project repositories. It applies verification checks to affected code, ensuring that formatting, linting, type-checking, builds, and tests are validated before merging changes.

Do I need Nx targets configured to run code quality checks on affected code?▼

No, you do not need Nx targets configured to run code quality checks. The verification process discovers Nx targets if present, but it relies primarily on reading CLAUDE.md and falls back to CI configs or project files to run the checks.

Related Skills

Explore More Software Engineering Skills→
t6adevt6adev
3

sandbox-check

Detect network and filesystem sandbox constraints across project files.

Community
Advanced
aimasteraccaimasteracc
46

land-and-deploy

Merge PRs after CI passes and trigger production deployment with canary health checks.

Community
Advanced
nrwlnrwl
1.4k

nx-run-tasks

Automate Nx workspace tasks across single or multiple projects.

Official
Intermediate
jpeggdevjpeggdev

setup

Detect project language, framework, and tooling, then configure tribunal interactively.

Community
Advanced