skills.rest
JeremyDev87
JeremyDev87COMMUNITY
Explore all skills by this author →
WebsiteGitHub

cross-repo-issues

Route issues to upstream repositories after user confirmation.

31|3|Updated Dec 12, 2025
Search Tags:#routing#github#mapping#confirmation#issue-management#upstream
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill cross-repo-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-repo-issues
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/cross-repo-issues
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill cross-repo-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects when an issue discovered in this repository belongs upstream, and routes it to the appropriate upstream repository with explicit user confirmation.

Core Features & Use Cases

  • Detects whether an issue should be reported upstream based on repository structure or dependency relationships.
  • Maps local files or packages to their upstream repositories using a configurable upstreamRepos mapping.
  • Guides the user through a mandatory three-phase workflow: detect, confirm, and create in the target upstream repository, with a linked tracking issue when appropriate.

Quick Start

Follow the three steps to route an issue upstream.

Frequently Asked Questions about cross-repo-issues

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

FAQPage Schema
How do I route GitHub issues to an upstream repository?▼

Routing GitHub issues upstream requires mapping local repository files or packages to their correct targets using an upstreamRepos mapping, then detecting the target and creating the issue in the upstream repository with a linked tracking issue.

What is the process for moving an issue to an upstream dependency repository?▼

Moving an issue to an upstream dependency repository follows a mandatory three-phase workflow: detect the target upstream repository, confirm the routing action with explicit user approval, and create the issue upstream.

How do I report bugs in third-party dependencies to the correct upstream GitHub repository?▼

Reporting bugs in third-party dependencies uses configurable upstreamRepos mapping to identify the correct upstream GitHub target, ensuring issues discovered in forks or monorepos are routed and created in the proper upstream repository.

Does cross-repo issue routing require user confirmation before creating the upstream issue?▼

Yes, cross-repo issue routing strictly requires explicit user confirmation before creating an issue in the upstream repository, enforcing a three-phase workflow of detection, user confirmation, and cross-repo issue creation.

Can I map issues from a monorepo to multiple upstream repositories?▼

Mapping issues from a monorepo to multiple upstream repositories is supported by configuring the upstreamRepos mapping, which detects whether an issue belongs upstream based on repository structure or dependency relationships.

When should I not use cross-repo issue routing for upstream dependencies?▼

Cross-repo issue routing should not be used when an issue is specific to the local repository rather than belonging to upstream forks, monorepos, or third-party dependencies, as the detection mechanism targets upstream sources only.

Related Skills

Explore More Software Engineering Skills→
luongnv89luongnv89
787

skill-upstream-pr

Fork a GitHub skill repository, run the auto-improvement loop, and draft an upstream PR with metrics.

Community
Advanced
bnufwbnufw

plan

Draft structured repo-local plans and generate linked CSV issue references.

Community
Intermediate
Minara-AIMinara-AI
28

setup-matt-pocock-skills

Standardize repository configuration for AI agents across GitHub, GitLab, and markdown workflows.

Official
Intermediate
Keiji-MiyakeKeiji-Miyake

tech-storyteller

Extract development narratives from Git history and repository documentation.

Community
Basic