run-checks

Run minimal static checks and builds for server, web, admin, apple, cli, and proto changes.

680|24|Updated Sep 6, 2024
One-click install
npx skills add https://github.com/inline-chat/inline --skill run-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-checks
Source: https://github.com/inline-chat/inline/tree/main/.codex/skills/run-checks
Command: npx skills add https://github.com/inline-chat/inline --skill run-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the validation of code changes by running a minimal, focused set of static checks and targeted builds/tests before a production push, reducing risk and rework.

Core Features & Use Cases

  • Scope-aware checks: analyzes touched areas across server/web/admin/apple/cli/proto and skips irrelevant work.
  • Pre-check orchestration: triggers proto generation when proto changes are touched, installs necessary dependencies, and runs typecheck, lint, and tests for affected components.
  • Result-driven workflow: summarizes pass/fail status, highlights actionable failures, and guides next steps before release.

Quick Start

Run pre-push validations on the current changes across the repository. If proto changes are detected, include the generated diffs in the report and proceed with targeted steps for the impacted areas.

Frequently Asked Questions about run-checks

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

FAQPage Schema
How do I run pre-push static checks and builds before a production push?

Pre-push static checks are executed by identifying touched areas across server, web, admin, apple, cli, and proto, running targeted builds and linting to validate changes before production deployment.

What is scope-aware repository validation and how does it avoid unnecessary work?

Scope-aware repository validation analyzes touched components and skips irrelevant work by applying fast, targeted typechecks and tests only to impacted areas like server, web, or proto.

How do I validate proto changes and trigger proto generation in CI pre-checks?

When proto changes are detected, proto generation is automatically triggered during pre-check orchestration, including the generated diffs in the validation report for impacted components.

Can I use targeted typecheck and lint for specific components like admin or cli?

Yes, targeted typecheck and lint can be applied across server, web, admin, apple, cli, and proto changes to guide fast validation and avoid unnecessary work across the repository.

What is the best way to summarize static check failures and guide next steps?

A result-driven workflow summarizes pass and fail statuses, highlights actionable failures, and guides the next steps required to resolve issues before proceeding with a release.