How do I install the Check Push skill?

Run npx skillmds@latest add pockethost/check-push in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Check Push safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Check Push?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Check Push free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Check Push?

pockethost (@pockethost) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Check Push by pockethost — Agent Skill

Name: Check Push
Author: pockethost

File contents

check:push

Prevents .husky/pre-push failures. Command mirrors CI quality + mothership hook freshness (no dashboard build).

Run

pnpm check:push

Equivalent to:

pnpm lint && \
  pnpm --filter pockethost check:types && \
  pnpm --filter phio check:types && \
  pnpm --filter @pockethost/dashboard check:types && \
  pnpm check:mothership-hooks && \
  pnpm test

Procedure

Run pnpm check:push from repo root.
On failure, fix only what the output names. Re-run the failing step (or full check:push before push).
Repeat until exit code 0.
Only then suggest git push or create the PR.

Do not use --no-verify unless the user explicitly asked to skip hooks.

Failure triage

Prettier (`pnpm lint`)

pnpm lint:fix

Or format touched files only. Re-run pnpm lint.

Types — pockethost

pnpm --filter pockethost check:types

Types — phio

pnpm --filter phio check:types

Types — dashboard

pnpm --filter @pockethost/dashboard check:types

Mothership hooks stale

pnpm --filter pockethost-mothership-app build

Commit regenerated pb_hooks/, then re-run pnpm check:mothership-hooks.

Tests

pnpm test

For a single file: pnpm vitest run path/to/file.test.ts

Dashboard build (CI only)

Pre-push does not run dashboard build. svelte-check will not catch prerender failures.

Run pnpm check:ci (adds dashboard build) before push or merge when you changed any of:

Files under packages/dashboard/src/routes/(static)/
$page.url, page.url.searchParams, query-string banners, or URL-driven UI
+layout.ts / +page.ts with prerender, ssr, or csr
svelte.config, Vite config, or static adapter settings

pnpm check:ci

Prerender build failure

Symptom: Cannot access url.searchParams on a page with prerendering enabled or Error: 500 /some-route during vite build.

Fix: see Prerender (static routes) in .cursor/rules/dashboard-ux.mdc. Usually guard with browser or move the read to onMount. Re-run pnpm check:ci.

Pair with commit

After /commit or when commits are done and push is next, run check:push before git push.

Report

State pass/fail, what you fixed, and that the branch is safe to push (or what still blocks).

---name: check-pushdescription: Run pnpm check:push (lint, types, tests) before git push or PR-ready work. Use when the user asks to push, open a PR, reports a failed pre-push hook, or when substantive code changes are finished and push is next.---# check:pushPrevents `.husky/pre-push` failures. Command mirrors CI quality + mothership hook freshness (no dashboard build).## Run```bashpnpm check:push```Equivalent to:```bashpnpm lint && \ pnpm --filter pockethost check:types && \ pnpm --filter phio check:types && \ pnpm --filter @pockethost/dashboard check:types && \ pnpm check:mothership-hooks && \ pnpm test```## Procedure1. Run `pnpm check:push` from repo root.2. On failure, fix only what the output names. Re-run the **failing step** (or full `check:push` before push).3. Repeat until exit code 0.4. Only then suggest `git push` or create the PR.Do not use `--no-verify` unless the user explicitly asked to skip hooks.## Failure triage### Prettier (`pnpm lint`)```bashpnpm lint:fix```Or format touched files only. Re-run `pnpm lint`.### Types — pockethost```bashpnpm --filter pockethost check:types```### Types — phio```bashpnpm --filter phio check:types```### Types — dashboard```bashpnpm --filter @pockethost/dashboard check:types```### Mothership hooks stale```bashpnpm --filter pockethost-mothership-app build```Commit regenerated `pb_hooks/`, then re-run `pnpm check:mothership-hooks`.### Tests```bashpnpm test```For a single file: `pnpm vitest run path/to/file.test.ts`## Dashboard build (CI only)Pre-push does **not** run dashboard `build`. **`svelte-check` will not catch prerender failures.**Run **`pnpm check:ci`** (adds dashboard `build`) before push or merge when you changed any of:- Files under `packages/dashboard/src/routes/(static)/`- `$page.url`, `page.url.searchParams`, query-string banners, or URL-driven UI- `+layout.ts` / `+page.ts` with `prerender`, `ssr`, or `csr`- `svelte.config`, Vite config, or static adapter settings```bashpnpm check:ci```### Prerender build failureSymptom: `Cannot access url.searchParams on a page with prerendering enabled` or `Error: 500 /some-route` during `vite build`.Fix: see **Prerender (static routes)** in [.cursor/rules/dashboard-ux.mdc](../../rules/dashboard-ux.mdc). Usually guard with `browser` or move the read to `onMount`. Re-run `pnpm check:ci`.## Pair with commitAfter `/commit` or when commits are done and push is next, run `check:push` **before** `git push`.## ReportState pass/fail, what you fixed, and that the branch is safe to push (or what still blocks).

Frequently asked questions

Check Push