name	scope-refactor
description	Scope a refactoring task by counting affected files, lines, and dependencies before starting
context	fork
agent	Explore
allowed-tools	Grep, Glob, Bash, Read

Scope the following refactoring task: $ARGUMENTS

Produce a refactoring impact report:

Matches: Use tools/ai/scope_changes.sh to count affected files and lines
File list: Every file that needs to change, grouped by crate
Dependency order: Which files should be changed first? (common/ before server/, proto before everything)
Risk assessment:
- Does this touch conflict zones? (proto, Cargo.toml, server.rs)
- Could this break existing tests?
- Does this require proto regeneration?
Effort estimate: How many subagents would this need? (use rule: >10 changes across >3 files = subagents)
Recommendation: Direct edit, subagent delegation, or separate branch?

Be concise. Use counts and file lists, not full file contents.

Más de este repositorio

mismo repositorio

Inspect the PostgreSQL schema, tables, and data for a running lifelog instance

Validate, stage, and commit current changes with a conventional commit message

Diagnose and fix build failures systematically

Explain how a specific part of the lifelog architecture works with diagrams and data flow

Trace a data modality end-to-end from proto definition through collector, server, and storage

Fix a GitHub issue end-to-end with tests and validation

name	scope-refactor
description	Scope a refactoring task by counting affected files, lines, and dependencies before starting
context	fork
agent	Explore
allowed-tools	Grep, Glob, Bash, Read

Scope the following refactoring task: $ARGUMENTS

Produce a refactoring impact report:

Matches: Use tools/ai/scope_changes.sh to count affected files and lines
File list: Every file that needs to change, grouped by crate
Dependency order: Which files should be changed first? (common/ before server/, proto before everything)
Risk assessment:
- Does this touch conflict zones? (proto, Cargo.toml, server.rs)
- Could this break existing tests?
- Does this require proto regeneration?
Effort estimate: How many subagents would this need? (use rule: >10 changes across >3 files = subagents)
Recommendation: Direct edit, subagent delegation, or separate branch?

Be concise. Use counts and file lists, not full file contents.