Repository navigation
fix(pi): preserve requested coverage within Context7 call budget - #3154
jmclaughlin724 wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The new sentence introduces potentially conflicting guidance (“other authorized sources”) relative to earlier “don’t rely on training data / prefer Context7” instructions, which could lead to unverified answers being presented as complete.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates the Context7 Docs skill’s constraint wording to clarify that the 3-call limit applies to Context7 tool invocations and should not silently truncate the user’s requested conceptual coverage.
Changes:
- Expands the “3 calls per question” constraint to explicitly distinguish tool-call budget from requested coverage expectations.
File summaries
| File | Description |
|---|---|
| packages/pi/skills/context7-docs/SKILL.md | Clarifies the meaning and implications of the 3-call Context7 constraint in the skill guidance. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| ## Constraints | ||
|
|
||
| - Do not call either tool more than 3 times per question. | ||
| - Do not call either tool more than 3 times per question. This limits Context7 calls, not requested coverage: use other authorized sources for remaining concepts, or identify the unresolved coverage without claiming completion. |
|
Thank you for the PR. This changes only the pi skill and sends the agent to other sources, which conflicts with the skill's prefer-Context7 rule and makes it differ from the other skills and prompts. Closing. |
The packaged Pi skill says "Do not call either tool more than 3 times per question." For a multi-concept question, that cap can silently drop explicitly requested coverage: the skill also requires one query-docs call per distinct concept, so four concepts cannot all be covered within three calls. This keeps the call budget but clarifies that it limits Context7 calls, not requested coverage — use other authorized sources for remaining concepts, or state the unresolved coverage instead of claiming completion. Verified: the only behavioral change is one sentence in the skill guidance; no runtime code touched.