skills.rest
windyroad
windyroadOFFICIAL
Explore all skills by this author →
WebsiteGitHub

wr-itil:report-upstream

File local docs/problems tickets against upstream repositories with templates.

4|1|Updated Apr 7, 2026
Search Tags:#security#ADR#cross-reference#upstream#problem-reporting
One-click install
npx skills add https://github.com/windyroad/agent-plugins --skill wr-itil-report-upstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wr-itil:report-upstream
Source: https://github.com/windyroad/agent-plugins/tree/main/packages/itil/skills/report-upstream
Command: npx skills add https://github.com/windyroad/agent-plugins --skill wr-itil-report-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to file a local problems ticket against an upstream repository, discover upstream issue templates, and route security-classified tickets through SECURITY.md, while back-writing a cross-reference into the local ticket.

Core Features & Use Cases

  • Supports problem-first upstream intake by locating and applying upstream templates, with structured default bodies when no template exists.
  • Handles dedup checks, cross-references, and back-write of Reported Upstream to synchronize downstream and upstream tracking.
  • Routes security-classified issues via the upstream's SECURITY.md or, if absent, prompts for secure-path actions and manual guidance.

Quick Start

Submit a downstream ticket using the /wr-itil:report-upstream invocation to file an upstream report for a local problem.

Frequently Asked Questions about wr-itil:report-upstream

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

FAQPage Schema
How do I report a local problem ticket to an upstream repository?▼

Reporting a local problem ticket upstream involves locating the local ticket and filing an issue against the upstream repository using a matched template or structured default. The Skill then back-writes a cross-reference link into the local ticket.

How does upstream problem routing handle security-classified tickets?▼

Upstream problem routing handles security-classified tickets by routing them through the upstream's SECURITY.md file when available. If absent, it prompts for secure-path actions and manual guidance.

Can I use this to classify local issues as bugs, features, or questions?▼

Yes, you can classify local issues as bugs, features, or questions. The Skill uses problem-first scoring to automatically determine the most appropriate issue classification before routing.

What is the best way to cross-reference downstream and upstream tracking tickets?▼

The best way to cross-reference downstream and upstream tracking is to create or comment on the upstream issue, generate a cross-reference, and back-write the link into the local ticket under a Reported Upstream section.

What happens when an upstream repository has no issue templates?▼

When an upstream repository has no issue templates, the upstream routing process falls back to a structured default body. This ensures the issue is still filed with organized information.

Do I need a local docs problems ticket to report upstream?▼

Yes, you need a local docs/problems/<NNN>-*.md ticket to report upstream. The Skill locates this local ticket to extract context and back-write the cross-reference after filing the upstream issue.

Related Skills

Explore More Legal & Compliance Skills→
im9im9
1

adr

Generate ADR documents with context, alternatives, and trade-offs.

Community
Intermediate
mizchimizchi
320

upstream-fix-and-pin

Pin downstream dependencies to upstream git refs and track merge SHAs.

Community
Advanced
lawdroidAIlawdroidAI
22

client-intake

Produce structured civil legal aid intake summaries after eligibility screening.

Official
Advanced
osouthgateosouthgate
4

skill-feedback

Log skill usage feedback to local JSONL files and generate reports.

Community
Intermediate