RuView is a WiFi sensing platform that uses disturbances in radio signals, captured by low-cost ESP32 sensors, to detect presence, movement, breathing, and heart rate without cameras or wearables. It is intended for spatial monitoring and smart-home integrations. The catalogue add-ons support workflows for operating and integrating RuView.
Borrowing it
Nothing to install: this file belongs to ruvnet/RuView. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/RuView/main/.claude/commands/hooks/pre-edit.mdgit clone --depth 1 https://github.com/ruvnet/RuViewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ruvnet/ruview/pre-edit)<a href="https://agentmods.dev/commands/ruvnet/ruview/pre-edit"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/pre-edit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ruvnet/ruview/pre-edit"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/pre-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00551 |
| Opus 5.5 | $0.00000 | $0.00220 |
| Sonnet 5.5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
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 1mo 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 12 lines differ
- pre-edit — 100% identical, 0 lines differ
- pre-edit — 100% identical, 0 lines differ
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": []
}
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.
- 1mo ago First seen · 114 lines · 0 tokens per session scan A 43d0a4f70b4a
pre-edit is a command published in the GitHub repository ruvnet/RuView (98,353 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
bom
Generate or analyze Bill of Materials from KiCad project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.