verify-in-repo

Validate open GitHub issues against a current branch using the GitHub API.

Updated May 31, 2026
One-click install
npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill verify-in-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-in-repo
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/verify-in-repo
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill verify-in-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the verification of GitHub issues by checking if they are still open defects in the current branch, saving time by preventing unnecessary steps in the fix workflow.

Core Features & Use Cases

  • Read-only Verification: Quickly determine if a GitHub issue is a real, unfixed defect.
  • Integration with GitHub: Uses GitHub API to check issue status, labels, and pull requests.
  • Use Case: When you receive a bug report, use the verify-in-repo skill to ensure it hasn't already been resolved or is not a duplicate, avoiding unnecessary actions.

Quick Start

Run the verify-in-repo skill with the issue ID, e.g., verify-in-repo 1234.

Frequently Asked Questions about verify-in-repo

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

FAQPage Schema
How do I check if a GitHub issue is still a valid bug before starting work?

To verify a GitHub issue is still a valid bug, you can run the `verify-in-repo` skill with the issue ID. It checks the issue status against the current branch to determine if the defect is real or already resolved.

How does issue verification against a current branch work?

Issue verification works by utilizing the GitHub API to check issue state, labels, and pull requests. It analyzes commits and PRs against the current branch to confirm whether the reported defect still exists.

Can I use this GitHub issue triage process to reduce false positives?

Yes, you can use this GitHub issue triage process to reduce false positives. It performs read-only verification to ensure reported bugs have not already been fixed, preventing unnecessary steps in your workflow.

Do I need write access to the repository to validate open issues?

You do not need write access to validate open issues. The verification process is read-only, utilizing the GitHub API to check issue status and PR history without modifying the repository.

What's the best way to automate issue triage for software development?

The best way to automate issue triage is using the `verify-in-repo` skill. It streamlines workflow optimization by validating open GitHub issues against your current branch to quickly identify actual bugs.