estimator

Structure repository audits into scoped chunks with effort estimates.

4|3|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Artifex1/auditor-addon --skill estimator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimator
Source: https://github.com/Artifex1/auditor-addon/tree/main/skills/estimator
Command: npx skills add https://github.com/Artifex1/auditor-addon --skill estimator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimation and scoping for audits is often manual and error-prone. This Skill provides a structured, phase-driven approach to map files into chunks, classify scope, and produce reliable effort estimates.

Core Features & Use Cases

  • Structured Discovery, Chunking, and Metrics workflow for audits.
  • Full-scope estimation with Discovery, Explore/Metrics/Report, and Diff-scope with Discovery/Review/Report.
  • Checkpoint-driven progression to pause and confirm scope before proceeding.
  • Generates actionable estimates and per-chunk risk signals to plan engagements.

Quick Start

Provide the repository to estimate and specify whether to run a full-scope or diff-scope estimation to begin.

Frequently Asked Questions about estimator

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

FAQPage Schema
How do I estimate the effort needed for a full codebase audit?

Estimate codebase audit effort by running a structured discovery process that maps files into chunks, classifies scope, and generates per-chunk risk metrics through phased progression.

What is the best way to scope a diff-scope review for recent code changes?

Scope a diff-scope review by targeting only the changed code, running through discovery, review, and reporting phases to produce reliable effort estimates for the specific modifications.

Can I pause an audit estimation to confirm the scope before proceeding?

You can pause an audit estimation using checkpoint-driven progression, which enforces phase-based workflows to confirm scope and file categorization before continuing to exploration and metrics.

How does file chunking work for codebase audit estimation?

File chunking for audit estimation works by categorizing repository files into structured segments during the discovery phase, enabling targeted metrics generation and per-chunk risk signaling for the engagement.

Does this estimation approach support time-bound audit engagements?

It supports time-bound audit engagements by structuring discovery, exploration, metrics, and reporting phases to quantify effort and generate actionable estimates tailored to specific time constraints.