web-push-checks

Run pnpm lint:web before pushing AX-WMS web changes.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill web-push-checks-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-push-checks
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/web-push-checks
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill web-push-checks-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushing unvalidated AX-WMS web changes can introduce frontend lint errors, broken code, or pre-existing issues to the remote repository, disrupting team workflows and requiring unnecessary rollbacks.

Core Features & Use Cases

  • Pre-push lint validation: Automatically triggers the required pnpm lint:web check for all modifications to the web area before any push or merge request operation.
  • Context-aware reporting: Distinguishes between new lint failures caused by current changes and pre-existing issues, and only requests user confirmation for push when failures are unrelated to current work.
  • Scope-limited activation: Only applies the validation step when changes impact the web area, skipping unnecessary checks for unrelated code modifications.

Quick Start

Use the web-push-checks skill to verify frontend lint compliance before pushing your AX-WMS web changes.

Frequently Asked Questions about web-push-checks

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

FAQPage Schema
How do I run a pre-push check for frontend lint errors in AX-WMS?

To run a pre-push check for frontend lint errors in AX-WMS, use this skill to automatically execute pnpm lint:web before any push or merge request. This prevents unvalidated web changes from disrupting team workflows.

Why does pnpm lint:web fail on git push when I did not modify the web area?

The pnpm lint:web validation is scope-limited, meaning it only activates when your changes impact the AX-WMS web area. If your modifications are unrelated to web code, the pre-push check is automatically skipped to avoid unnecessary failures.

How to handle pre-existing lint failures during an AX-WMS git push?

To handle pre-existing lint failures during an AX-WMS git push, the skill distinguishes between new errors and pre-existing issues. It only requests user confirmation of push intent when failures are unrelated to your current changes, allowing you to proceed safely.

Does the web-push-checks skill validate code quality for all commit operations?

Yes, the web-push-checks skill validates code quality for all commit, push, and merge request operations. It ensures frontend lint compliance by requiring pnpm lint:web execution and providing clear reporting of lint results.

Can I skip lint validation for non-web modifications in AX-WMS?

Yes, you can skip lint validation for non-web modifications in AX-WMS because the skill features scope-limited activation. It automatically bypasses the pnpm lint:web check when your changes do not impact the web area, skipping unnecessary code quality validations.