validate-issue

Trace GitHub issue claims to specific code locations and evaluate solution feasibility.

45|7|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/richkuo/rk-skills --skill validate-issue-richkuo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-issue
Source: https://github.com/richkuo/rk-skills/tree/main/skills/validate-issue
Command: npx skills add https://github.com/richkuo/rk-skills --skill validate-issue-richkuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents wasted engineering effort by verifying the factual accuracy of GitHub issues before work begins, ensuring that proposed fixes are based on the actual state of the codebase rather than potentially stale or incorrect author descriptions.

Core Features & Use Cases

  • Evidence-Based Validation: Traces every factual claim in an issue to specific file and line references in the repository.
  • Architectural Review: Evaluates the feasibility and self-consistency of proposed fixes, identifying potential regressions or design flaws.
  • Complexity Scoring: Automatically calculates a complexity score to route the issue to the appropriate model and effort level.

Quick Start

Use the validate-issue skill to check the latest open issue in the current repository for factual accuracy and architectural feasibility.

Frequently Asked Questions about validate-issue

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

FAQPage Schema
How do I validate GitHub issue claims against my actual codebase?

Validating GitHub issues involves tracing factual assertions to specific file and line references in the repository, ensuring proposed fixes match the actual codebase state before engineering work begins.

Can I automate issue triage to evaluate architectural feasibility?

Automating issue triage evaluates the feasibility and self-consistency of proposed technical solutions, identifying potential regressions or design flaws to prevent wasted engineering effort during architectural review.

How does code review automation calculate complexity estimation for open issues?

Complexity estimation for open issues is calculated by automatically scoring the issue, routing it to the appropriate processing model and effort level based on the evaluated technical requirements.

What is evidence-based verification for software development workflows?

Evidence-based verification for software development workflows cross-references factual issue claims with existing pull requests and specific code locations to identify potential implementation risks and verify accuracy.