Menu
Use to fetch current documentation for technical topics like APIs, libraries, or tools mentioned in conversation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to create a new pull request, update an existing PR's body, open a draft PR, or preview a PR body locally before pushing.
Use when executing implementation plans with independent tasks in the current Pi session using fresh subagents and review loops
Create a new Pi task folder for a specific task or feature development. Use when the user wants to start a new task, plan a feature, or asks to create a task file.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute with review checkpoints
Use when you have an approved design or requirements for a multi-step task, before touching code
| name | source-check |
| description | Use to fetch current documentation for technical topics like APIs, libraries, or tools mentioned in conversation. |
| disable-model-invocation | true |
Fetch current documentation for technical topics in context.
/source-check — fetch docs for technical topics in recent conversation/source-check [topic] — fetch docs for a specific topicFetch current info for:
Skip: conceptual discussions, architecture questions, opinion-based topics.
Scan recent conversation for technical topics that would benefit from current documentation. Prioritize:
List each topic as a brief phrase.
Dispatch a general-purpose subagent with:
Fetch current documentation for these technical topics:
1. [topic 1]
2. [topic 2]
...
For each topic:
1. Generate 1-2 targeted search queries (include library name, version if relevant)
2. Use WebSearch to find current docs (prefer official docs, changelogs, release notes)
3. If needed, use WebFetch on official docs URL for details
4. Summarize current state/behavior
Return ONLY this format:
## Current Documentation
### [Topic 1]
[Current state/behavior summary - 2-3 sentences]
Source: [Official Docs](url)
### [Topic 2]
[Current state/behavior summary - 2-3 sentences]
Source: [Changelog](url)
If a topic has changed recently, note what changed.
Present subagent results. Use fetched documentation to inform subsequent responses.
## Current Documentation
### [Topic]
[Current state/behavior summary]
Source: [Source Name](url)
### Notable Changes
- [Recent change if relevant]
Omit Notable Changes if nothing recent.
If no technical topics found:
No technical topics identified in recent context.
Single topic:
Runs after render by default. Cleanup function runs before next effect and on unmount. Dependencies array controls when effect re-runs.
Source: React Docs
Multiple topics with changes:
Native ESM fully supported. Use "type": "module" in package.json or .mjs extension. require() still works in CommonJS files.
Source: Node.js Docs
require() of ESM modules behind flag (--experimental-require-module)Resume normal conversation. Use fetched documentation to inform subsequent responses.