Checking Upstream
Find existing upstream knowledge or work before taking action.
- Infer the project and precise problem from the conversation and any command
arguments. Ask one focused question only if either is unclear.
- Identify the canonical upstream repository and tracker, not just a fork or
package mirror.
- Search the issue tracker, including closed issues, and the open pull
request, merge request, patch, or equivalent change queue. Try a few
focused variants: the exact error or symbol, the symptom, and the affected
component.
- Read plausible matches enough to verify relevance. Note their status,
latest meaningful activity, linked work, decisions, workarounds, and
blockers.
- Report concisely:
- canonical upstream and tracker URLs;
- relevant matches with title, status, URL, and why they match;
- an assessment: active work, discussion only, previously resolved, or no
relevant match;
- any useful conclusions, workarounds, or missing information.
Prefer tracker-native search or APIs, with web search as a fallback. If no
matches are found, state the searches performed and note that this does not
prove no report exists.
Do not modify code, file or comment on an issue, or open a change request
unless explicitly asked.
1---2name: checking-upstream3description: Checks the canonical upstream issue tracker and open pull requests, merge requests, or equivalent change queues for existing reports, discussion, or work on a problem just discussed. Use before diagnosing, fixing, or reporting an apparent open-source problem to avoid duplicate effort and missed context.4---56# Checking Upstream78Find existing upstream knowledge or work before taking action.9101. Infer the project and precise problem from the conversation and any command11 arguments. Ask one focused question only if either is unclear.122. Identify the canonical upstream repository and tracker, not just a fork or13 package mirror.143. Search the issue tracker, including closed issues, and the open pull15 request, merge request, patch, or equivalent change queue. Try a few16 focused variants: the exact error or symbol, the symptom, and the affected17 component.184. Read plausible matches enough to verify relevance. Note their status,19 latest meaningful activity, linked work, decisions, workarounds, and20 blockers.215. Report concisely:22 - canonical upstream and tracker URLs;23 - relevant matches with title, status, URL, and why they match;24 - an assessment: active work, discussion only, previously resolved, or no25 relevant match;26 - any useful conclusions, workarounds, or missing information.2728Prefer tracker-native search or APIs, with web search as a fallback. If no29matches are found, state the searches performed and note that this does not30prove no report exists.3132Do not modify code, file or comment on an issue, or open a change request33unless explicitly asked.
aspiers