ll-refine-issue

To refine vague issue tickets, this Skill scans your repository to gather relevant context and performs gap analysis to identify missing technical requirements. It synthesizes this context into actionable development steps for implementation readiness.

The best way to prepare undocumented software issues is to bridge knowledge gaps by performing automated codebase research. This process updates issue documentation with repository context and missing technical requirements to ensure implementation clarity.

Yes, issue tracking refinement requires integration with git and local issue management tools. These dependencies are necessary to automatically scan repository history and synthesize context into actionable development steps.

Yes, you can use this for automated gap analysis on a specific issue ID. The Skill researches the affected files and history for the provided ID, identifying missing information needed before development begins.

Your issue ticket lacks actionable implementation steps due to ambiguity and missing context in the raw documentation. This Skill resolves this by researching the codebase to update requirements and provide a clear plan for the fix.

The limitations of automated issue documentation refinement include its operational scope, which is strictly confined to issue tracking and technical task preparation. It relies entirely on existing git history and local issue management tools to synthesize context.