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: >-4 Checks the canonical upstream issue tracker and open pull requests, merge5 requests, or equivalent change queues for existing reports, discussion, or6 work on a problem just discussed. Use before diagnosing, fixing, or7 reporting an apparent open-source problem to avoid duplicate effort and8 missed context.9---1011# Checking Upstream1213Find existing upstream knowledge or work before taking action.14151. Infer the project and precise problem from the conversation and any command16 arguments. Ask one focused question only if either is unclear.172. Identify the canonical upstream repository and tracker, not just a fork or18 package mirror.193. Search the issue tracker, including closed issues, and the open pull20 request, merge request, patch, or equivalent change queue. Try a few21 focused variants: the exact error or symbol, the symptom, and the affected22 component.234. Read plausible matches enough to verify relevance. Note their status,24 latest meaningful activity, linked work, decisions, workarounds, and25 blockers.265. Report concisely:27 - canonical upstream and tracker URLs;28 - relevant matches with title, status, URL, and why they match;29 - an assessment: active work, discussion only, previously resolved, or no30 relevant match;31 - any useful conclusions, workarounds, or missing information.3233Prefer tracker-native search or APIs, with web search as a fallback. If no34matches are found, state the searches performed and note that this does not35prove no report exists.3637Do not modify code, file or comment on an issue, or open a change request38unless explicitly asked.
aspiers