oss:issue-analysis

To analyze an OSS issue, you extract actionable requirements from the issue text and explore the codebase structure to pinpoint exact files and functions for modification. This process translates issue requirements into a concrete modification plan.

The best way to turn issue requirements into a code change plan is by performing structured issue analysis that aligns requirements with project conventions and traces execution paths. This yields a precise map of code locations needing modification.

Codebase exploration analyzes project structure and conventions to identify impact areas for a specific issue. By tracing execution paths and call flows, it verifies the feasibility of changes and links exact functions to issue requirements.

Yes, you can trace execution paths to verify the feasibility of proposed code changes. Tracing call paths ensures the located files and functions correctly align with the issue requirements before you begin implementation.

You need to provide either an issue URL or a detailed issue description to generate a modification plan. This input allows the analysis to extract the necessary requirements and map them to exact code locations.

When an OSS issue lacks clear requirements, issue requirement extraction derives actionable tasks from the issue text and discussions. It translates vague descriptions into structured requirements aligned with the codebase structure.