pre-push

A pre-push command that reviews all changes since the branch was last synchronized with its remote copy.

In plain words
What is it for?
Use it before pushing code to compare changes, run the review process, check changed files, and recommend whether to push or fix issues first.
Why use it?
It helps catch serious review findings and project-rule violations before changes are sent to the shared repository.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/cdeust/ai-architect-mcp-codebase/pre-push
Clone the repo
git clone --depth 1 https://github.com/cdeust/ai-architect-mcp-codebase

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 121 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00121
Opus 5 $0.00000 $0.00060
Sonnet 5 $0.00000 $0.00024
Haiku 4.5 $0.00000 $0.00012

Measured 2d ago against content hash e0992db889e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pre-push scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/quality/pre-push.md · 20 lines

What it actually says

Pre-Push Review

Run the full review skill on all changes since last push.

Instructions

  1. Determine the remote tracking branch.

  2. Compute the diff: git diff <tracking>...HEAD

  3. Run the /review skill (skills/engineering/review.md) on the diff.

  4. If critical findings exist, list them and recommend fixing before push.

  5. Run tools/zetetic-checker.sh --files on all changed files.

  6. Report: review findings + zetetic violations + recommendation (push / fix first).

$ARGUMENTS

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 20 lines · 0 tokens per session scan A e0992db889e1

Subscribe to this mod's changes

pre-push is a command published in the GitHub repository cdeust/ai-architect-mcp-codebase (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 121 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.