pre-edit

A pre-edit hook, meaning an automatic check that runs before a file is changed.

In plain words
What is it for?
Use it to validate a file’s syntax, check for conflicts, create a backup, and automatically assign an agent before editing.
Why use it?
It can catch syntax problems and merge conflicts early, while assigning the edit to a suitable specialist agent.

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/f-amine/vibe-stack/pre-edit
Clone the repo
git clone --depth 1 https://github.com/f-amine/vibe-stack

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 551 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00551
Opus 5 $0.00000 $0.00275
Sonnet 5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

Measured yesterday against content hash 43d0a4f70b4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pre-edit 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 yesterday.

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.

Origin

This is a copy

100% identical to pre-edit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/hooks/pre-edit.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

hook pre-edit

Execute pre-edit validations and agent assignment before file modifications.

Usage

npx claude-flow hook pre-edit [options]

Options

  • --file, -f <path> - File path to be edited
  • --auto-assign-agent - Automatically assign best agent (default: true)
  • --validate-syntax - Pre-validate syntax before edit
  • --check-conflicts - Check for merge conflicts
  • --backup-file - Create backup before editing

Examples

Basic pre-edit hook

npx claude-flow hook pre-edit --file "src/auth/login.js"

With validation

npx claude-flow hook pre-edit -f "config/database.js" --validate-syntax

Manual agent assignment

npx claude-flow hook pre-edit -f "api/users.ts" --auto-assign-agent false

Safe editing with backup

npx claude-flow hook pre-edit -f "production.env" --backup-file --check-conflicts

Features

Auto Agent Assignment

  • Analyzes file type and content
  • Assigns specialist agents
  • TypeScript → TypeScript expert
  • Database → Data specialist
  • Tests → QA engineer

Syntax Validation

  • Pre-checks syntax validity
  • Identifies potential errors
  • Suggests corrections
  • Prevents broken code

Conflict Detection

  • Checks for git conflicts
  • Identifies concurrent edits
  • Warns about stale files
  • Suggests merge strategies

File Backup

  • Creates safety backups
  • Enables quick rollback
  • Tracks edit history
  • Preserves originals

Integration

This hook is automatically called by Claude Code when:

  • Using Edit or MultiEdit tools
  • Before file modifications
  • During refactoring operations
  • When updating critical files

Manual usage in agents:

# Before editing files
npx claude-flow hook pre-edit --file "path/to/file.js" --validate-syntax

Output

Returns JSON with:

{
  "continue": true,
  "file": "src/auth/login.js",
  "assignedAgent": "auth-specialist",
  "syntaxValid": true,
  "conflicts": false,
  "backupPath": ".backups/login.js.bak",
  "warnings": []
}

Read the full file on GitHub · 114 lines

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. yesterday First seen · 114 lines · 0 tokens per session scan A 43d0a4f70b4a

Subscribe to this mod's changes

pre-edit is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 551 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pre-edit, differing in 0 lines, and is treated as a copy.