skills.rest
rameshkumarchouhanr
rameshkumarchouhanrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

effort

Estimates implementation effort for GitHub issues as SMALL, MEDIUM, or LARGE.

Updated Aug 26, 2026
Search Tags:#code analysis#github issues#effort estimation#issue triage#json output#gemini cli#bug sizing
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill effort-rameshkumarchouhanr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effort
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/effort
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill effort-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Triaging incoming issues requires a consistent estimate of how much engineering work a fix will take, but manual sizing is subjective and inconsistent across reviewers. ## Core Features & Use Cases - Structured Effort Sizing: Classifies an issue into SMALL (1 day or less), MEDIUM (2-3 days), or LARGE (3+ days) buckets with detailed reasoning. - Code-Aware Analysis: Considers the issue title and body together with code exploration output such as discovered source files, coupled UI components, and test files. - Domain-Specific Rubric: Applies calibrated criteria for the Gemini CLI codebase, covering Ink UI bugs, async flow issues, node-pty and signal handling, MCP transport, and CI/CD overhauls. - Use Case: A triage worker receives a new bug report about terminal flickering in the interactive UI; the skill analyzes the issue plus explored code and returns a JSON estimate of MEDIUM with reasoning about React/Ink state synchronization complexity. ## Quick Start Estimate the implementation effort for this issue using the effort skill and return the JSON result.

Frequently Asked Questions about effort

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

FAQPage Schema
How do I estimate implementation effort for a GitHub issue automatically?▼

Provide the issue title and body along with code exploration output listing relevant source files, UI components, and tests. The skill returns a JSON object with an effort_estimate of SMALL, MEDIUM, or LARGE plus detailed reasoning.

What effort levels does issue triage estimation use?▼

Three levels are used: SMALL for fixes of one day or less like typos and config changes, MEDIUM for two-to-three-day work like state management or async flow bugs, and LARGE for three-plus-day efforts like PTY handling or architecture refactors.

Can intermittent or hard-to-reproduce bugs be rated as small effort?▼

No. The rubric explicitly forbids rating intermittent, flickering, platform-specific, or cross-environment issues as SMALL, because reproduction and testing overhead significantly increases the real cost of the fix.

What input does the effort estimation skill require?▼

It requires the issue content (title and body) and the code exploration output, meaning the discovered source files, coupled UI components, and test files related to the issue. Both inputs together drive the estimate.

What kinds of issues count as large effort estimates?▼

LARGE covers platform-specific complexities like node-pty and POSIX signal handling, core architecture and protocol work such as Scheduler or MCP transport refactors, CI/CD infrastructure overhauls, and major performance or memory investigations.

Related Skills

Explore More Software Engineering Skills→
google-geminigoogle-gemini
106.8k

code_explorer

Locate primary source files, related components, and test files for bug reports.

Official
Intermediate
arcasilesgrouparcasilesgroup
54

ai-triage

Syncs Git metadata and triages GitHub Issues and Azure Boards tasks.

Official
Advanced
0xHoneyJar0xHoneyJar

triage

Triages user signals and error reports to identify affected code paths and estimate blast radius.

Official
Intermediate
Razmik-KutinavaRazmik-Kutinava

Story Point Estimator

Guide agile teams in estimating story points using Planning Poker and Fibonacci sequencing.

Community
Intermediate