Index of every page on this site: llms.txt
All skills
google-gemini avatar

/effort

@eecccfc
by google-geminigoogle-gemini/gemini-cli109k stars
14,968
Run it yourself

Estimates the implementation effort required to address the given issue.

  • 1 file
  • 3 KB
  • Updated 4 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/google-gemini/gemini-cli/effort

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈20 tokens for metadata: the name and description. ≈753 when used: this file.

Description uses 1.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈81 characters, or 1.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Effort Estimator Instructions

Analyze the issue content (title, body) AND the code exploration output (the discovered source files, coupled UI components, and test files) to estimate the effort required to implement a fix.

JSON Output Format:

{
  "effort_estimate": "SMALL" | "MEDIUM" | "LARGE",
  "effort_reasoning": "Detailed explanation of why this estimate was chosen."
}

Effort Levels:

SMALL (1 day or less):

  • Trivial Logic & Config: Schema updates (Zod), feature flag toggles, adding missing fields to package.json or settings.json.
  • UI/Aesthetic Adjustments: Fixing minor layout bugs in Ink components (e.g., adding flexShrink, correcting padding in a single Box), text color changes.
  • Documentation & Strings: Typos, log message updates, CLI argument descriptions.
  • Localized Bug Fixes: Single-file logic errors, straightforward promise rejections (e.g., wrapping a known failure in a try/catch), simple regex or string parsing fixes.
  • Unhandled Errors with Obvious Fixes: Issues with provided stack traces or obvious offending lines where the root cause and fix are clear. MEDIUM (2-3 days):
  • React/Ink State Management: Complex component lifecycle issues (memory leaks in the UI), terminal redraw flickering, or state synchronization between the CLI's internal input buffer and the interactive React components.
  • Asynchronous Flow & Integration: Resolving complex Promise chains, ERR_STREAM_PREMATURE_CLOSE, debugging IDE companion extensions (VS Code, Android Studio) or resolving hanging HTTP requests/IPC between the CLI and external plugins, timeouts in non-interactive/ACP modes.
  • Tooling & Output Parsers: Modifying how tools parse streaming stdout/stderr buffers, adding new built-in tools that don't require native bindings.
  • Cross-Component & Cross-Package Refactors: Any fix or change that spans across packages/cli and packages/core (such as unifying event handlers, hooks, or UI state across package boundaries). LARGE (3+ days):
  • Platform-Specific Complexities (PTY/Signals): Any issue involving node-pty, child_process.spawn, pseudo-terminal exhaustion (ENXIO), raw mode terminal desyncs, or POSIX signal forwarding (SIGINT/SIGTERM).
  • Core Architecture & Protocols: Refactoring the Scheduler, Agent-to-Agent (A2A) protocol implementation, low-level MCP (Model Context Protocol) transport mechanisms.
  • CI/CD Infrastructure Overhauls: Major redesign of release pipelines or runner execution environments with a large blast radius across production builds.
  • Performance & Memory: Diagnosing massive disk/memory leaks, severe boot time regressions, high-throughput streaming optimizations (e.g., voice streaming pipelines).

Note: Any bug that is described as intermittent, flickering, difficult to reproduce, platform-specific, or requiring cross-environment setups (e.g., involving the VS Code IDE companion, GCA plugin, or Android Studio) MUST NOT be rated as effort/small because of the increased overhead of testing and reproducing.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at eecccfc. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 10 hours ago.

Activeupdated 4 months ago

README badge

README badge for google-gemini/gemini-cli/effort