skills.rest
ArthTech-AI
ArthTech-AIOFFICIAL
Explore all skills by this author →
GitHub

precheck

Run local pre-push tests on changed hooks, skills, and manifests.

Updated Aug 23, 2026
Search Tags:#git#testing#pull request#pre-push#ci#revert-check
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill precheck-arthtech-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: precheck
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/precheck
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill precheck-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch broken changes locally before pushing, so you avoid slow CI round-trips and prevent avoidable failures from reaching a pull request.

Core Features & Use Cases

  • Revert Safety Check: Runs a strict revert check first to detect accidental rollbacks of recently merged work.
  • Change-Aware Test Selection: Looks at what changed and chooses the relevant mechanical test suites instead of running everything blindly.
  • Push-Ready Workflow: Guides you through testing, then committing, pushing, creating a PR, merging, and cleaning up once checks pass.
  • Use Case: A developer changes a skill file, runs this Skill, and gets the right safety tests before the branch is pushed.

Quick Start

Use the precheck skill to inspect my changed files, run the matching local tests, and tell me whether it is safe to push.

Frequently Asked Questions about precheck

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

FAQPage Schema
How do I run local pre-push tests to catch CI failures before opening a pull request?▼

To catch CI failures before opening a pull request, you can run local pre-push tests using change-aware suite selection. This inspects changed files and executes only the relevant mechanical tests to ensure safe code integration.

What is a strict revert check in git pre-push workflows?▼

A strict revert check in git pre-push workflows detects accidental rollbacks of recently merged work before pushing code. It serves as an initial safety gate to prevent overwritten features from reaching a remote branch.

Can I run targeted tests for changed hooks and manifests instead of the full test suite?▼

Yes, you can run targeted tests for changed hooks and manifests through change-aware test selection. This mechanism evaluates modified files and chooses the matching mechanical test suites rather than blindly running the entire test suite.

What is the best way to manage a feature-branch workflow from commit to merge?▼

The best way to manage a feature-branch workflow is following a guided push-ready sequence: run tests, commit, push, create a PR, merge, and execute cleanup steps. This ensures checks pass before integration.

How does branch-aware suite selection work for brownfield fixtures?▼

Branch-aware suite selection for brownfield fixtures works by analyzing your feature-branch changes and selecting the corresponding mechanical tests. This targeted approach validates modified install flows and fixtures without unnecessary overhead.

Related Skills

Explore More Software Engineering Skills→
shmily1012shmily1012
1

using-git-worktrees

Create an isolated git worktree for a feature branch with safety checks.

Community
Advanced
arjitj2arjitj2

resolve-merge-conflicts

Resolves pull request merge conflicts by merging the base branch and pushing the updated branch.

Community
Advanced
yongwoonyongwoon
8

ywc-create-pr

Automate Git feature branch commits, security validation, and draft pull request creation.

Community
Advanced
markmhendricksonmarkmhendrickson
27

push

Push the current Git branch to origin with submodule scoping and pre-push checks.

Community
Intermediate