web-push-checks

Run frontend lint checks before pushing AX-WMS web changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AX-WMS web changes must pass frontend lint before pushing. Codex uses this skill when preparing to commit or push web changes, or when a user requests remote deployment using terms like 'push please' or 'MR please'.

Core Features & Use Cases

  • Pre-push lint enforcement for web-area changes.
  • Clear reporting of any lint failures with offending files and reasons.
  • No-ops if no web changes were touched.

Quick Start

Run pnpm lint:web before pushing 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 automate frontend lint checks before pushing web changes?

You can automate frontend lint checks before pushing by running pnpm lint:web, which enforces code quality rules and reports any failures with offending files and reasons before remote deployment.

What happens if my pre-push lint check fails on web code?

When a pre-push lint check fails on web code, the process halts the remote deployment and reports the specific lint failures. It provides actionable details including the offending files and the exact reasons for the violations.

Does the pre-push lint check run when no web code is affected?

No, the pre-push lint check automatically skips and no-ops when no web code is affected. This ensures that developers only encounter lint enforcement during scenarios where actual web area changes are being pushed.

How do I enforce code quality for AX-WMS web updates before a remote push?

To enforce code quality for AX-WMS web updates before a remote push, the automation intercepts push requests and runs frontend lint validation. This guarantees that only lint-compliant web changes are committed and deployed remotely.

What is the best way to handle lint enforcement for frontend web deployments?

The best way to handle lint enforcement for frontend web deployments is to automate the check during the pre-push phase. This catches code quality issues early by validating web changes before they reach the remote repository.