ll-verify-issues

Validating bug reports against a codebase requires cross-referencing issue documentation claims with existing source code. This skill performs automated verification checks to test assertions and identify if reports are still applicable or have been superseded by recent changes.

Checking backlog issue relevance involves comparing documented feature requests against the current implementation. This verification process identifies stale reports that misinterpret system logic or are no longer reproducible, filtering out inaccurate issues before development begins.

Verifying issue tracking metadata synchronization requires accessing the repository file system to perform automated checks. This skill compares issue file assertions against the actual state of the codebase to ensure documentation remains accurate and relevant.

Automating issue file verification for software maintenance is achieved by integrating this skill into development lifecycles. It automatically tests claims from issue documentation against current source code, ensuring developers avoid wasting time on inaccurate or stale bug reports.

Repository file system access is required for issue verification to perform automated checks. The skill needs this access along with issue tracking metadata to cross-reference documented claims with the existing source code implementation.

Issue documentation becomes inaccurate when recent code changes supersede existing bug reports or alter system logic. This skill identifies these discrepancies by validating issue files against codebase reality, filtering out reports that no longer match current implementation.