Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .changes/context7/docs-upstream-context7-revendor-e2230d61.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
bump: patch
---

### Changed

- **`/context7:lookup` synced to upstash/context7 `4087030`.** The vendored `find-docs` and `context7-cli` baselines are refreshed, and `metadata.upstream-version` names that commit. Upstream replaced its `/facebook/react` example library ID with `/reactjs/react.dev`, since `/facebook/react` now returns a redirect and no docs; the examples in the lookup and CLI references use the new ID.
4 changes: 2 additions & 2 deletions plugins/context7/skills/lookup/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ disable-model-invocation: false
allowed-tools:
- "Bash(ctx7 --version*)"
metadata:
upstream-version: upstash/context7@ceaf5f91f48949eaa6e4da5e66f3f59d1b44556d
synced: 2026-11-03
upstream-version: upstash/context7@4087030ad2dc16578130e2dab1e48ba735f8ea38
synced: 2026-11-16
workflow-stage: research
summary: Look up current library docs, API references, and examples via Context7
shell: bash
Expand Down
14 changes: 7 additions & 7 deletions plugins/context7/skills/lookup/context/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,24 +96,24 @@ Whether and what the CLI sends as telemetry is [Context7 CLI § Telemetry](https
On Windows with Git Bash / MSYS2, any CLI argument starting with `/` is rewritten to a Windows path. When you run:

```bash
ctx7 docs /facebook/react "useEffect cleanup"
ctx7 docs /reactjs/react.dev "useEffect cleanup"
```

Git Bash converts `/facebook/react` → `C:/Program Files/Git/facebook/react` before the CLI sees it. The CLI correctly rejects the malformed ID:
Git Bash converts `/reactjs/react.dev` → `C:/Program Files/Git/reactjs/react.dev` before the CLI sees it. The CLI correctly rejects the malformed ID:

```text
✖ Invalid library ID: "C:/Program Files/Git/facebook/react"
✖ Invalid library ID: "C:/Program Files/Git/reactjs/react.dev"
```

**Always prefix `ctx7 docs` calls with `MSYS_NO_PATHCONV=1`:**

```bash
MSYS_NO_PATHCONV=1 ctx7 docs /facebook/react "useEffect cleanup"
MSYS_NO_PATHCONV=1 ctx7 docs /reactjs/react.dev "useEffect cleanup"
```

- Prefix disables MSYS path conversion for that one invocation
- No-op on macOS/Linux, so it is safe to always include
- Double-slash workaround (`//facebook/react`) does **not** work. ctx7 rejects it as malformed
- Double-slash workaround (`//reactjs/react.dev`) does **not** work. ctx7 rejects it as malformed
- `ctx7 library` is unaffected (its first argument doesn't start with `/`)
- `ctx7 search --library /org/project` passes an argument starting with `/` too, so prefix it the
same way; this follows from the same rewrite and has not been tested on Windows
Expand All @@ -126,10 +126,10 @@ Output goes to stdout in formatted text (with ANSI color codes) or JSON with `--

```bash
# Filter docs for a specific keyword
MSYS_NO_PATHCONV=1 ctx7 docs /facebook/react "hooks" | grep -A3 -i useEffect
MSYS_NO_PATHCONV=1 ctx7 docs /reactjs/react.dev "hooks" | grep -A3 -i useEffect

# Strip ANSI for clean grep output
MSYS_NO_PATHCONV=1 ctx7 docs /facebook/react "hooks" | sed 's/\x1b\[[0-9;]*m//g' | grep useEffect
MSYS_NO_PATHCONV=1 ctx7 docs /reactjs/react.dev "hooks" | sed 's/\x1b\[[0-9;]*m//g' | grep useEffect

# Dump to disk (keeps context clean; echo the path in the same call — the docs
# output is redirected, so the path is the only thing the next Read can go on)
Expand Down
2 changes: 1 addition & 1 deletion plugins/context7/skills/lookup/context/lookup.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ Do not silently fall back to training data. Always tell the user why Context7 wa

## Common mistakes

- Library IDs require a `/` prefix: `/facebook/react` not `facebook/react`
- Library IDs require a `/` prefix: `/reactjs/react.dev` not `reactjs/react.dev`
- Always run `library` / `resolve-library-id` first. `ctx7 docs react "hooks"` fails without a valid ID
- Use descriptive queries, not single words
- Do not include secrets, personal data, proprietary code, stack traces, or internal identifiers in queries. Send distilled library/topic terms only
Expand Down
2 changes: 1 addition & 1 deletion plugins/context7/skills/lookup/vendor/cli/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,5 +57,5 @@ export CONTEXT7_API_KEY=your_key

## Common Mistakes

- Library IDs require a `/` prefix — `/facebook/react` not `facebook/react`
- Library IDs require a `/` prefix — `/reactjs/react.dev` not `reactjs/react.dev`
- Always run `ctx7 library` first — `ctx7 docs react "hooks"` will fail without a valid ID
4 changes: 2 additions & 2 deletions plugins/context7/skills/lookup/vendor/find-docs/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ The available versions are listed in the `library` command output. Use the close
Retrieves up-to-date documentation and code examples for the resolved library.

```bash
npx ctx7@latest docs /facebook/react "How to clean up useEffect with async operations"
npx ctx7@latest docs /reactjs/react.dev "How to clean up useEffect with async operations"
npx ctx7@latest docs /vercel/next.js "How to add an authentication proxy to app router"
npx ctx7@latest docs /prisma/prisma "How to define one-to-many relations with cascade delete"
```
Expand Down Expand Up @@ -159,7 +159,7 @@ Do not silently fall back to training data — always tell the user why Context7

## Common Mistakes

- Library IDs require a `/` prefix — `/facebook/react` not `facebook/react`
- Library IDs require a `/` prefix — `/reactjs/react.dev` not `reactjs/react.dev`
- Always run `npx ctx7@latest library` first — `npx ctx7@latest docs react "hooks"` will fail without a valid ID
- Use descriptive queries, not single words — `"React useEffect cleanup function"` not `"hooks"`
- One topic per query — split `"routing and auth and caching"` into a separate `docs` command per concept, unless the question is about how they interact
Expand Down
Loading