assess

Assess bug reports to identify gaps and propose a reproduction plan.

3|38|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ambient-code/workflows --skill assess-ambient-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assess
Source: https://github.com/ambient-code/workflows/tree/main/workflows/bugfix/.claude/skills/assess
Command: npx skills add https://github.com/ambient-code/workflows --skill assess-ambient-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This stage helps teams achieve a shared understanding of a bug report before any work begins, reducing miscommunication and unnecessary effort.

Core Features & Use Cases

  • Reads issue context, description, and discussion to identify gaps and ambiguities.
  • Proposes a clear plan with next steps and potential risks for review.
  • Produces a structured assessment that can gate the next phases in the bugfix workflow.

Quick Start

Review the bug report and present a concise assessment including gaps and a proposed plan, before starting reproduction or fixes.

Frequently Asked Questions about assess

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

FAQPage Schema
What is bug report assessment in software triage?

Bug report assessment identifies gaps and ambiguities in issue descriptions to achieve shared understanding before action. It reviews conversation context and artifacts to guide planning, propose reproduction steps, and gate subsequent bugfix phases.

How do I clarify a bug report before starting a fix?

To clarify a bug report before fixing, review the issue context and discussion to identify missing information, then produce a structured assessment with proposed reproduction steps and a concrete plan for risk evaluation.

Does the bug report assessment phase execute code or run tests?

The bug report assessment phase enforces no code execution during evaluation. It strictly analyzes issue descriptions and artifacts to produce a structured plan and risk assessment, preventing premature or unnecessary code execution before gaps are resolved.

What's the best way to identify gaps in an issue description?

The best way to identify gaps in an issue description is by analyzing the issue context, discussion history, and related repository artifacts to articulate a shared understanding and highlight missing reproduction steps or ambiguities.

Can I use a structured assessment artifact to gate a bugfix workflow?

You can use a structured assessment artifact to gate a bugfix workflow by reviewing its identified gaps, proposed plan, and risk assessment to ensure team alignment before authorizing subsequent reproduction or fix implementation phases.