Searching Sourcegraph
ClineOfficialPublished by Cline
- Skill
- Tool integration
- Software development
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to using Sourcegraph MCP tools for code exploration, debugging, and development. It emphasizes disciplined search workflows, starting with narrow scopes to improve precision and efficiency. The guide covers tool selection logic, query patterns, and best practices for chaining operations like searching, reading files, and tracing references to minimize token usage and maximize context accuracy.
What it does
- Provides a decision framework for selecting the right search tool based on user intent.
- Defines scoping strategies to limit searches to specific repositories, files, or languages.
- Outlines efficient workflows for feature implementation, bug fixing, and system understanding.
- Offers specific query patterns for common development tasks like finding React hooks or API routes.
- Establishes best practices for interpreting search results and minimizing redundant tool calls.
- Integrates with specialized workflows for debugging, code review, and deep system analysis.
When to use it
- When you need to find specific implementations or patterns within a large codebase.
- When troubleshooting errors, build failures, or runtime exceptions.
- When you need to understand how a specific feature or system component works.
- When reviewing pull requests or changesets to ensure consistency.
- When you need to identify who worked on specific code or which repositories a contributor has touched.
Advantages
- Reduces token consumption by promoting precise, scoped search queries.
- Ensures consistency by encouraging the reuse of existing patterns and utilities.
- Provides a logical, repeatable process for debugging and code exploration.
- Helps maintain context by chaining search, read, and reference-tracing operations.
- Prevents common mistakes like searching across unnecessary repositories.
Usage examples
- “How does the authentication flow work in our backend repository?”
- The agent uses deepsearch to identify relevant files, reads the core authentication logic, and summarizes the flow using the codebase's own terminology.
- “Find all usages of the 'UserSession' interface in the frontend.”
- The agent applies a keyword_search scoped to the frontend repository and file type, then lists the relevant files and line numbers.
- “I am getting a null pointer exception in the payment service, help me debug.”
- The agent extracts the error symbol, searches for the error site, traces the call chain with find_references, and checks recent commits for regressions.
- “Which repositories has the user 'jdoe' contributed to recently?”
- The agent uses get_contributor_repos to identify active repositories for the user, allowing for scoped searches in subsequent steps.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/cline/searching-sourcegraph/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip searching-sourcegraph.zip -d .agents/skills
Documentation by Cline
Searching Sourcegraph
Search before you build. Existing patterns reduce tokens, ensure consistency, and surface tested solutions.
Tool Selection Logic
Start here:
Know the exact symbol or pattern? →
keyword_searchKnow the concept, not the code? →
nls_searchNeed to understand how/why? →
deepsearch→deepsearch_readTracing a symbol's usage? →
find_referencesNeed full implementation? →
go_to_definition→read_fileNeed to know what repos a user has worked on? →
get_contributor_repos
| Goal | Tool |
|---|---|
| Concepts/semantic search | nls_search |
| Exact code patterns | keyword_search |
| Trace usage | find_references |
| See implementation | go_to_definition |
| Initiate a deep search | deepsearch |
| Read deep search results | deepsearch_read |
| Read files | read_file |
| Browse structure | list_files |
| Find repos | list_repos |
| Search commits | commit_search |
| Track changes | diff_search |
| Compare versions | compare_revisions |
| Find repos a user has worked on | get_contributor_repos |
Scoping (Always Do This)
repo:^github.com/ORG/REPO$ # Exact repo (preferred)
repo:github.com/ORG/ # All repos in org
file:.*\.ts$ # TypeScript only
file:src/api/ # Specific directory
file:.*\.test\.ts$ -file:__mocks__ # Tests, exclude mocksStart narrow. Expand only if results are empty.
Combine filters: repo:^github.com/myorg/backend$ file:src/handlers lang:typescript
Context-Aware Behaviour
When the user provides a file path or error message:
Extract symbols, function names, or error codes
Search for those exact terms first
Trace references if the error involves a known symbol
When the user asks "how does X work":
Use
deepsearchto initiate the search, thendeepsearch_readto retrieve resultsFollow up with
read_fileon key files mentioned in the response
When the user asks who worked on something or what repos a contributor has touched:
Use
get_contributor_reposwith one or more usernames to discover their active repositoriesThen scope subsequent searches to those repos
When the user is implementing a new feature:
Search for similar existing implementations first
Read tests for usage examples
Check for shared utilities before creating new ones
When troubleshooting an error, build failure, or runtime exception:
Extract exact symbols, error codes, or log lines from the stack trace or build output
Search for the error site, then trace the full call chain with
find_referencesCheck recent changes with
diff_searchandcommit_searchearly — regressions are commonIdentify all affected code paths and services before proposing a fix
When fixing a bug:
Extract exact symbols from the error message or stack trace
Search for the error site, then trace the full call chain with
find_referencesCheck recent changes with
diff_searchandcommit_searchearly — regressions are commonFind all affected code paths before writing the fix
Read existing tests to understand intended behaviour
Workflows
For detailed step-by-step workflows, see:
workflows/implementing-feature.md— when building new featuresworkflows/understanding-code.md— when exploring unfamiliar systemsworkflows/debugging-issue.md— when troubleshooting errors, build failures, stack traces, support issues, or runtime exceptionsworkflows/fixing-bug.md— when fixing bugs with extensive Sourcegraph searchworkflows/code-review.md— when reviewing a pull request or changeset
Efficiency Rules
Minimise tool calls:
Chain searches logically: search → read → references → definition
Don't re-search for the same pattern; use results from prior calls
Prefer
keyword_searchovernls_searchwhen you have exact terms (faster, more precise)
Batch your understanding:
Read 2-3 related files before synthesising, rather than reading one and asking questions
Use
deepsearch+deepsearch_readfor "how does X work" instead of multiple keyword searches
Avoid common token waste:
Don't search all repos when you know the target repo
Don't use
deepsearchfor simple "find all" queries —keyword_searchis fasterDon't re-read files you've already seen in this conversation
Query Patterns
| Intent | Query |
|---|---|
| React hooks | file:.*\.tsx$ use[A-Z].*= \( |
| API routes | file:src/api app\.(get|post|put|delete) |
| Error handling | catch.*Error|\.catch\( |
| Type definitions | file:types/ export (interface|type) |
| Test setup | file:.*\.test\. beforeEach|beforeAll |
| Config files | file:(webpack|vite|rollup)\.config |
| CI/CD | file:\.github/workflows deploy |
For more patterns, see query-patterns.md.
Output Formatting
Search results:
Present as a brief summary, not raw tool output
Highlight the most relevant file and line
Include a code snippet only if it directly answers the question
Code explanations:
Start with a one-sentence summary
Use the codebase's own terminology
Reference specific files and functions
Recommendations:
Present as numbered steps if actionable
Link to specific patterns found in the codebase
Note any existing utilities that should be reused
Common Mistakes
| Mistake | Fix |
|---|---|
| Searching all repos | Add repo:^github.com/org/repo$ |
| Too many results | Add file: pattern or keywords |
| Missing relevant code | Try nls_search for semantic matching |
| Not understanding context | Use deepsearch_read |
| Guessing patterns | Read implementations with read_file |
Principles
Start narrow, expand if needed
Chain tools: search → read → find references → definition
Check tests for usage examples
Read before generating
Files
- ATTRIBUTION.mdAdded by AutoGineer848 B
- LICENSELicence file added by AutoGineer10.5 KiB
- SKILL.md6.1 KiB
- examples/common-searches.md1.6 KiB
- query-patterns.md2.2 KiB
- workflows/code-review.md4.2 KiB
- workflows/debugging-issue.md3.3 KiB
- workflows/fixing-bug.md3.7 KiB
- workflows/implementing-feature.md1.2 KiB
- workflows/understanding-code.md1.1 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by the Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding any notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Copyright 2026 Cline Bot Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Cline
- Publisher
- Cline (Official)
- Source
- cline/skills · skills/searching-sourcegraph · commit 2637846
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Cline.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download searching-sourcegraph.zip