ether-scope-estimate

Estimates and reconciles lines-of-code scope for surgical fixes using a local learning database.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill ether-scope-estimate-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ether-scope-estimate
Source: https://github.com/arayaroma/ether/tree/main/skills/ether-scope-estimate
Command: npx skills add https://github.com/arayaroma/ether --skill ether-scope-estimate-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scope creep makes small fixes balloon into wide-ranging edits that are hard to review and risky to merge. This Skill forces an agent to record a min/max lines-of-code estimate before writing any implementation code, then reconcile the actual diff against that estimate after verification, so oversized changes cannot close silently. ## Core Features & Use Cases - Pre-implementation estimation: Searches prior estimates in the local .ether/learning.db via ether learn search, then records a min/max LOC estimate as a problem entry before any code is written. - Post-verify reconciliation: Measures actual changed LOC with git diff --stat and compares it against the recorded range, recording a confirming observation when the estimate holds. - Mandatory overrun handling: When actual LOC exceeds the max, requires a recorded cause, prevention solution, and generalizable learning before the change can be considered done. - Use Case: A builder subagent is assigned a bug fix. Before touching code it records an estimate of 10-40 LOC; after tests pass, the diff shows 95 lines, so it must document why (hidden coupling across call sites) and capture a prevention learning for future estimates. ## Quick Start Ask the agent to estimate the min/max lines of code for this fix, record it with ether learn, implement the change, and reconcile the actual diff against the estimate.

Frequently Asked Questions about ether-scope-estimate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate lines of code before writing a fix?▼

Read the task and tasks.md, name the smallest change satisfying the acceptance criteria, and state a min (floor for a contained fix) and max (ceiling allowing a couple of adjacent call sites). Record it with ether learn problem before writing any code.

How do I measure actual LOC changed after implementation?▼

Run git diff --stat against the pre-change commit and sum insertions plus deletions across all changed files, excluding generated files and lockfiles. Compare that total against the recorded min/max range.

What happens when actual LOC exceeds the estimate?▼

The overrun cannot close silently. You must record a cause explaining why it took more lines, a solution describing what would have kept it surgical, and a generalizable learning so future estimates of similar problems are calibrated.

Does ether-scope-estimate require network access?▼

No, it is fully offline. All estimate storage and search run through ether learn commands against a local SQLite file at .ether/learning.db, with no API calls or external services.

How are edited existing lines counted in LOC estimates?▼

Each edited existing line counts as roughly 2 LOC, one deletion plus one insertion in the diff. A signature change rippling through N call sites therefore costs about 2N LOC even though it looks trivial.