port-upstream-issues-ag

Harvest open issues from decolua/9router, reproduce them against OmniRoute, and classify for fix workflow.

44.0k|5.9k|Updated Feb 13, 2026

Search Tags:#github #nextjs #regression testing #issue triage #attribution #bug reproduction #porting

Ready to run

npx skills add https://github.com/diegosouzapw/OmniRoute --skill port-upstream-issues-ag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: port-upstream-issues-ag
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/port-upstream-issues-ag
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill port-upstream-issues-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves bugs reported on the upstream decolua/9router issue tracker by harvesting open issues, reproducing them against OmniRoute, and preparing local, fully attributed fix work—without ever interacting with upstream’s tracker.

Core Features & Use Cases

Upstream issue harvesting: Collects all open issues (or a user-specified subset) from decolua/9router and captures full metadata for triage.
OmniRoute reproduction + triage: Determines whether each issue is security, viable to fix, needs upstream feature-hand-off, or is not applicable due to implementation differences.
Fix workflow with attribution: Guides creating one branch per approved issue, adding a failing regression test first, and committing fixes with Reported-by attribution and a CHANGELOG entry for OmniRoute only.

Quick Start

Use the agent to harvest all open issues from decolua/9router, triage them against OmniRoute for reproducibility, then generate a plan for the specific issue numbers you approve for fixes.

Frequently Asked Questions about port-upstream-issues-ag

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

FAQPage Schema

How do I port upstream GitHub issues into local Next.js bug fixes?▼

Port upstream GitHub issues by harvesting open reports, reproducing them locally, and classifying whether to fix, hand off, or defer. This Skill automates triage and maps fixes to your TypeScript Next.js codebase layers with regression tests.

What is the workflow for reproducing upstream bugs before applying a fix?▼

Reproducing upstream bugs involves collecting issue metadata, testing the reported behavior against your local codebase, and triaging the results. The process determines if an issue is a security risk, viable for a local fix, or requires an upstream hand-off.

How to handle attribution and regression testing when porting bug reports?▼

Handle attribution by adding a Reported-by tag and a CHANGELOG entry for your local repository only. Regression testing requires writing a failing test first on a dedicated branch before committing the actual code fix.

Does this issue triage process interact with the upstream GitHub tracker?▼

No, the issue triage process strictly avoids interacting with the upstream GitHub tracker. It harvests public issue data for local reproduction and classification, ensuring all fix attribution and regression testing remains entirely within your local project.

When should I defer an upstream issue instead of creating a local fix?▼

You should defer an upstream issue when triage classification determines it is not applicable due to implementation differences. Issues are deferred if they require upstream feature hand-offs or do not reproduce against your specific codebase layers.