t1076: Update context7 agent with skill registry, telemetry disable, and package rename#1570
Conversation
…nd package rename - Update package name from @context7/mcp-server to @upstash/context7-mcp - Add Context7 skills registry awareness (search, install, suggest via ctx7 CLI) - Add skill discovery-to-aidevops import workflow documentation - Add telemetry disable guidance (CTX7_TELEMETRY_DISABLED=1) - Update MCP tool names to current API (query-docs) - Add Claude Code installation method and remote server connection - Add comparison table between ctx7 install and /add-skill import
Summary of ChangesHello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly updates the documentation for the Context7 agent, ensuring it reflects the latest upstream changes and introduces new capabilities. The primary goal is to enhance the integration of Context7 with AI assistants by providing clearer instructions for setup, skill management, and telemetry control, thereby improving the overall developer experience and alignment with current Context7 offerings. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
WalkthroughDocumentation update to the Context7 agent tool guide, replacing MCP server package references, introducing a Skills Registry workflow for skill search and installation, updating tool usage semantics, and expanding configuration guidance across multiple setup scenarios. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Tue Feb 17 19:09:10 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request significantly updates the documentation for the Context7 agent. It reflects an upstream package rename, introduces the new skills registry feature, and provides instructions for telemetry disablement. The changes are comprehensive and well-structured. I've added a couple of suggestions to improve the clarity of the new skill management commands to prevent potential user confusion.
|
|
||
| 1. **Search** the Context7 registry: `npx ctx7 skills search <query>` | ||
| 2. **Evaluate** trust score (7+ = high, 3-6.9 = medium, <3 = review carefully) | ||
| 3. **Import** into aidevops: `/add-skill <github-repo>` (e.g., `/add-skill anthropics/skills`) |
There was a problem hiding this comment.
There's a subtle inconsistency in the workflow. The ctx7 tool provides skill IDs with a leading slash (e.g., /supabase-community/supabase-custom-claims), but the /add-skill command examples use the path without the leading slash. This could confuse users. Please clarify that the leading slash should be removed from the skill ID before passing it to /add-skill, for instance by adding a note to the workflow steps.
|
|
||
| # Remove a skill | ||
| npx ctx7 skills remove pdf | ||
| /add-skill remove <name> |
There was a problem hiding this comment.
The placeholder <name> in the /add-skill remove <name> command is ambiguous. It's unclear if this refers to the original skill name, the repository name, or the name of the skill file created by aidevops. To improve clarity, please provide a concrete example based on the import example used earlier in the document.
| /add-skill remove <name> | |
| /add-skill remove supabase-custom-claims-skill |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.agents/tools/context/context7.md:
- Around line 21-45: The docs use the MCP tool name `query-docs` in the Quick
Reference but still reference `get-library-docs` throughout; update all
occurrences of `get-library-docs` to `query-docs` (including examples, Usage
Examples, Best Practices, Troubleshooting, Integration, Advanced Features and
any CLI snippets) so the symbol names match; search the document for
`get-library-docs`, replace with `query-docs`, and verify sample commands, code
blocks, and narrative text consistently use `query-docs` (and adjust any
surrounding phrasing that implies different arguments or behavior).
| - **Purpose**: Real-time access to latest library/framework documentation | ||
| - **Command**: `npx -y @context7/mcp-server@latest` | ||
| - **Built into Augment**: No setup needed, tools available directly | ||
| - **Package**: `@upstash/context7-mcp` (formerly `@context7/mcp-server`) | ||
| - **CLI**: `npx ctx7` for skills and setup commands | ||
| - **Telemetry**: Disable with `export CTX7_TELEMETRY_DISABLED=1` | ||
|
|
||
| **MCP Tools**: | ||
| - `resolve-library-id("next.js")` → Returns "/vercel/next.js" | ||
| - `get-library-docs("/vercel/next.js")` → Returns documentation | ||
| - `get-library-docs("/vercel/next.js", topic="routing")` → Topic-specific | ||
| - `get-library-docs("/vercel/next.js", tokens=15000)` → More detail | ||
| - `resolve-library-id` → Resolves library name to Context7 ID (e.g., "next.js" → "/vercel/next.js") | ||
| - `query-docs` → Retrieves documentation for a library ID with a query | ||
|
|
||
| **Common Library IDs**: | ||
| - Frontend: `/vercel/next.js`, `/facebook/react`, `/vuejs/vue` | ||
| - Backend: `/expressjs/express`, `/nestjs/nest` | ||
| - DB/ORM: `/prisma/prisma`, `/supabase/supabase`, `/drizzle-team/drizzle-orm` | ||
| - Tools: `/vitejs/vite`, `/typescript-eslint/typescript-eslint` | ||
|
|
||
| **Skills Registry**: Context7 hosts a searchable skills registry at [context7.com/skills](https://context7.com/skills). Search, install, and suggest skills for your project: | ||
|
|
||
| ```bash | ||
| npx ctx7 skills search react # Search registry | ||
| npx ctx7 skills suggest # Auto-suggest from project deps | ||
| npx ctx7 skills install /anthropics/skills pdf # Install a skill | ||
| ``` | ||
|
|
||
| Skills found in the Context7 registry can be imported into aidevops using `/add-skill`. See "Skill Discovery and Import" section below. | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat .agents/tools/context/context7.mdRepository: marcusquinn/aidevops
Length of output: 13963
Align all usage examples with the Quick Reference tool name (query-docs).
Quick Reference declares the MCP tool as query-docs, but all downstream examples—spanning Usage Examples, Best Practices, Troubleshooting, Integration, and Advanced Features sections—consistently use get-library-docs. This creates a direct reference mismatch that will mislead developers implementing the documented workflows.
Update the ~30+ instances of get-library-docs in examples and sections to query-docs to maintain documentation consistency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/tools/context/context7.md around lines 21 - 45, The docs use the MCP
tool name `query-docs` in the Quick Reference but still reference
`get-library-docs` throughout; update all occurrences of `get-library-docs` to
`query-docs` (including examples, Usage Examples, Best Practices,
Troubleshooting, Integration, Advanced Features and any CLI snippets) so the
symbol names match; search the document for `get-library-docs`, replace with
`query-docs`, and verify sample commands, code blocks, and narrative text
consistently use `query-docs` (and adjust any surrounding phrasing that implies
different arguments or behavior).
1 participant
Summary
@context7/mcp-serverto@upstash/context7-mcp(upstream rename)npx ctx7CLI/add-skillCTX7_TELEMETRY_DISABLED=1)query-docsreplacesget-library-docs)ctx7 skills installand/add-skillimportChanges
Single file:
.agents/tools/context/context7.md(+134/-32 lines)Testing
Closes #1569
Summary by CodeRabbit