estimate-assistant

Analyze git history and code complexity to estimate development tasks.

5|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/SteveFeldman/agents-skills --skill estimate-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate-assistant
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/estimate-assistant
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill estimate-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides data-driven task estimates by analyzing historical git data, code complexity, and similar past work, reducing guesswork in project planning.

Core Features & Use Cases

  • Git History Analysis: Leverages git log and gh pr to understand past development effort.
  • Code Complexity Assessment: Evaluates lines of code, cyclomatic complexity, and dependencies.
  • Similar Task Matching: Identifies comparable completed tasks to inform current estimates.
  • Use Case: When planning a new feature, use this Skill to get a realistic estimate by looking at how long similar features took in the past, considering code complexity and potential risks.

Quick Start

Use the estimate-assistant skill to analyze the task 'Implement user authentication flow'.

Frequently Asked Questions about estimate-assistant

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

FAQPage Schema
How do I estimate software development time using git history?

You can estimate software development time using git history by analyzing past commit logs, code complexity, and similar completed tasks to generate data-driven estimates for project planning.

Can I use GitHub CLI PR analysis to improve task estimation accuracy?

Yes, you can use GitHub CLI PR analysis to improve task estimation accuracy. The assistant leverages gh pr commands alongside git log data to understand past development effort and inform more realistic project estimates.

What is data-driven project planning and how does code complexity affect it?

Data-driven project planning uses historical git data and code complexity metrics like cyclomatic complexity and lines of code to reduce guesswork. Evaluating dependencies and matching similar past tasks provides realistic effort estimates.

Does the estimate-assistant skill work without dependencies?

Yes, the estimate-assistant skill works without external dependencies. It requires no additional packages, though accessing git repository data and the GitHub CLI for PR analysis enhances its estimation accuracy.

What's the best way to plan a new feature using historical development data?

The best way to plan a new feature using historical development data is to analyze similar completed tasks, evaluate code complexity and dependencies, and apply past development effort metrics to project current timelines realistically.