framework-issue-resolve

Triage upstream GitHub issues and generate maintainer review drafts.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill framework-issue-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: framework-issue-resolve
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/framework-issue-resolve
Command: npx skills add https://github.com/lync-cyber/CataForge --skill framework-issue-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers systematically process upstream GitHub issues from intake to closure, reducing manual triage work and preventing unresolved feedback from drifting across releases.

Core Features & Use Cases

  • Issue Triage: Pull issues, check versions, classify reports, and generate draft analysis artifacts for maintainer review.
  • Rooted Repair Workflow: Move from diagnosis to implementation through a controlled checkpoint process that separates analysis, approval, code changes, and closure.
  • Maintainer-Focused Closure: Produce standardized close comments and outcomes such as fixed, already-fixed, or wontfix, with traceable references to the triage draft.
  • Use Case: A maintainer receives a bug report from a downstream fork and uses this Skill to verify the report, document the evidence, implement the fix, and close the issue with a consistent upstream response.

Quick Start

Ask the assistant to triage the selected GitHub issue and generate the maintainer review draft with a clear verdict and next-step recommendation.

Frequently Asked Questions about framework-issue-resolve

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

FAQPage Schema
How do I automate GitHub issue triage for upstream repository maintenance?

Automating GitHub issue triage involves pulling upstream reports, checking versions, and classifying issues to generate maintainer-ready review drafts. This workflow reduces manual triage effort and prevents unresolved feedback from drifting across releases.

What is the best way to close upstream GitHub issues with traceable references?

The best way to close upstream GitHub issues with traceable references is to generate standardized close comments with outcomes like fixed, already-fixed, or wontfix. This process links closures directly to the initial triage draft for maintainer accountability.

How does version checking work when resolving bug reports from downstream forks?

Version checking during bug resolution compares the downstream fork's state against the upstream repository. This evidence collection step verifies whether a report is valid, already-fixed, or obsolete before planning any code changes.

Can I use a controlled workflow to separate issue diagnosis from code changes?

Yes, a rooted repair workflow separates issue diagnosis from code changes using controlled checkpoints. This process moves from analysis to approval, implementation, and closure actions to maintain structured repository maintenance.

What steps are needed to generate a maintainer review draft for a bug report?

Generating a maintainer review draft requires parsing the GitHub issue, performing version comparisons, and collecting evidence. The resulting draft provides a clear verdict and next-step recommendation for the maintainer's closure workflow.