Sourcegraph agent skills for Claude Code, Cursor and RevampKey

3 ready-made playbooks that teach an AI agent how to do real Sourcegraph work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect Sourcegraph

Connect Sourcegraph once and all 3 skills install themselves and stay up to date. Mac, Windows and Linux.

All 3 Sourcegraph skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereRead-only13 Sourcegraph tools

Use Sourcegraph with AI, safely and precisely

Guides an AI assistant through searching a Sourcegraph instance: it confirms the instance, repository and revision first, picks the right search or navigation tool, and reads the actual code before claiming anything. It stays read-only.

Use it when

You connect Sourcegraph to an AI assistant and want it to search correctly
You ask where a function is used across many repositories
Searches return nothing or too much and you need a narrower approach

Tools it uses

list_repos
keyword_search
nls_search
read_file
go_to_definition
find_references
commit_search
diff_search
compare_revisions
get_contributor_repos
deepsearch
deepsearch_read
list_files

Example

Where is the retry helper defined in our payments repository on the release tag, and who calls it?

Scope: sourcegraph.example.com, github.com/acme/payments at tag v2.4.0. The helper is defined in internal/retry/backoff.go at line 18 and is called from 4 places: charge.go:41, refund.go:77, webhook.go:103 and sync.go:29. I read each call site before listing it.

Use in RevampKeyRead the full skill →

Read-only8 Sourcegraph tools

Investigate when and why code behaviour changed in Sourcegraph

Works out when a behaviour changed and which commit caused it, by comparing release tags, searching commits and diffs, and reading the code at each revision. It is read-only and asks before changing the active instance or workspace.

Use it when

A bug appeared sometime between two releases and you need the commit that caused it
You want to know who or what removed a check or default
A function's output changed and you need the mechanism, not just the date

Tools it uses

list_repos
compare_revisions
commit_search
diff_search
find_references
read_file
go_to_definition
get_contributor_repos

Example

Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.

The change point is commit 7f3a2c in the export service, merged in v4.2.0 by a contributor who changed the default of skipNullDates from true to false. Callers that omit the flag now include rows with null dates. I read the code at the parent and at the commit to confirm the flip, and no other commit in the window touches that filter.

Use in RevampKeyRead the full skill →

Read-only4 Sourcegraph tools

Audit a code pattern across repositories

Sweeps many repositories for a pattern, reads each hit in context to confirm it, and reports verified counts with a clear statement of what was covered. It is read-only and never changes code.

Use it when

Find every repository still calling a deprecated API before removing it
Inventory where a config key or feature flag is read across the org
Check whether an unsafe construct appears on a release branch that is still deployed

Tools it uses

list_repos
keyword_search
nls_search
read_file

Example

Find every place we still call the legacy payments client across the backend repos, and tell me which are real calls versus tests or comments.

I searched 84 repositories on the main branch. 37 confirmed live calls to the legacy client, across 11 repositories. 9 hits were excluded as test fixtures and 4 as comments. The 2 remaining hits are in generated code I could not classify, so I've flagged them for review.

Use in RevampKeyRead the full skill →

Get all 3 without copying a file

RevampKey adds the skills when you connect Sourcegraph, updates them for you and removes them when you disconnect.

Download RevampKey

How Sourcegraph skills work

Connect Sourcegraph
The Sourcegraph MCP server gives the agent its tools.
Ask in plain words
“Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install Sourcegraph skills

In RevampKey the skills install themselves when you connect Sourcegraph. In other tools each skill is one folder with a SKILL.md file, and you also need the Sourcegraph MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect Sourcegraph. All 3 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.”
Download RevampKeyConnect Sourcegraph · 1 click
Get RevampKey to connect Sourcegraph
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Sourcegraph is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials change-history-investigation code-search-audit; do curl -fsSL --create-dirs -o .claude/skills/sourcegraph-$s/SKILL.md https://revampkey.com/marketplace/sourcegraph/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the Sourcegraph MCP server in Claude Code.

Run this in your project folder to add all 3 skills:

for s in essentials change-history-investigation code-search-audit; do
  curl -fsSL --create-dirs -o .claude/skills/sourcegraph-$s/SKILL.md https://revampkey.com/marketplace/sourcegraph/skills/$s/SKILL.md
done

Ask in plain language, for example “Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.”

Into the shared .agents/skills folder

Connect the Sourcegraph MCP server in Cursor.

Run this in your project folder to add all 3 skills:

for s in essentials change-history-investigation code-search-audit; do
  curl -fsSL --create-dirs -o .agents/skills/sourcegraph-$s/SKILL.md https://revampkey.com/marketplace/sourcegraph/skills/$s/SKILL.md
done

Ask in plain language, for example “Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.”

Into the shared .agents/skills folder

Connect the Sourcegraph MCP server in Codex.

Run this in your project folder to add all 3 skills:

for s in essentials change-history-investigation code-search-audit; do
  curl -fsSL --create-dirs -o .agents/skills/sourcegraph-$s/SKILL.md https://revampkey.com/marketplace/sourcegraph/skills/$s/SKILL.md
done

Ask in plain language, for example “Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.”

Into the shared .agents/skills folder

Connect the Sourcegraph MCP server in VS Code.

Run this in your project folder to add all 3 skills:

for s in essentials change-history-investigation code-search-audit; do
  curl -fsSL --create-dirs -o .agents/skills/sourcegraph-$s/SKILL.md https://revampkey.com/marketplace/sourcegraph/skills/$s/SKILL.md
done

Ask in plain language, for example “Between v4.1.0 and v4.3.0, our export started dropping rows with null dates. Find the commit that changed this and explain why.”

RevampKey or copy the files?

In RevampKey

One click when you connect Sourcegraph
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the Sourcegraph MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

Sourcegraph skills FAQ

What is a Sourcegraph agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each Sourcegraph skill describes one job, which Sourcegraph tools to use in which order, what to check first and when to stop and ask you.

Do the Sourcegraph skills change anything on their own?

3 of the 3 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in Sourcegraph.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect Sourcegraph; elsewhere you copy the folders into your project or skills directory.

Do I need the Sourcegraph MCP server too?

Yes. The skills tell the agent how to do the work; the Sourcegraph MCP server gives it the tools to do it. The Sourcegraph MCP setup guide covers every client.

Sourcegraph MCP server setup · This page as Markdown

Put Sourcegraph’s best workflows in your agent

Download RevampKey, connect Sourcegraph and ask your first question in about a minute.

Download RevampKey Connect Sourcegraph · 1 click

All 3 Sourcegraph skills

Use Sourcegraph with AI, safely and precisely

Use it when

Tools it uses

Investigate when and why code behaviour changed in Sourcegraph

Use it when

Tools it uses

Audit a code pattern across repositories

Use it when

Tools it uses

Get all 3 without copying a file

How Sourcegraph skills work

How to install Sourcegraph skills

RevampKey or copy the files?

In RevampKey

Copy into your project

Sourcegraph skills FAQ

Put Sourcegraph’s best workflows in your agent

Skills for related tools