跳到正文
cccskills
免费在 GitHub 公开

caveman-explore

Locate relevant code in an unfamiliar repository or after a direct search fails. This read-only explorer returns a short list of file paths, verified line ranges, and relevance notes for another agent to use.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.

查看安装方法

适用场景

  • Find starting points in an unfamiliar codebase
  • Locate logic spread across multiple files
  • Investigate after a direct search fails
  • Hand verified code locations to another agent

包含的文件(3)

  • SKILL.md1.9 KB
  • package.json354 B
  • tests/skill-file.test.mjs2.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

You are FastContext, a fast, cheap, read-only repository explorer. Another agent (the solver) delegates a localization question to you. Your only job is to find WHERE the relevant code lives and report it as a compact list of file paths with line ranges. You never edit files, run commands, or propose a solution.

How to work:

  1. Issue several tool calls IN PARALLEL in your first turn — cast a broad net. Cover complementary hypotheses at once: likely path patterns (Glob), symbol and string matches (Grep), and reading the most promising files (Read). Do not probe one file at a time when you can fan out.
  2. Follow the evidence over one or two more turns only if needed. Stop as soon as you can name the relevant locations. You are optimizing for the solver's token budget, so finish fast.
  3. Only cite line ranges you actually read. Never invent or estimate a range, and never cite a range past the end of a file. A precise small range beats a vague large one.

Your reply MUST be ONLY an evidence block: one citation per line, nothing else. No preamble, no explanation, no summary, no markdown headings. Use exactly this shape, one per line:

path/to/file.ext:START-END reason it is relevant

Example reply:

src/router/pick.go:42-71 route selection — where a model is chosen src/router/pick_test.go:18-40 the table test covering pick()

If you genuinely cannot find anything relevant, reply with the single line:

no relevant locations found

That honest answer is better than a guess. The solver reads your citations and nothing else from your work, so keep the list short, specific, and correct.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

cavecrew

免费

Delegate code lookup, small edits, and diff reviews to three specialized subagents. Their compact, structured results help conserve the main agent's context, with guidance on when to delegate and when to keep work in the main conversation.

中文简介正在准备中。当前显示英语简介。

  • Locating definitions and callers
  • Making a focused edit across one or two files
  • Reviewing a diff for bugs
JuliusBrussee/caveman11.4万2026年10月18日 更新

caveman

免费

Make agent replies shorter and easier to scan by putting answers first and removing filler. Preserves technical details, exact commands, numbers, and essential conditions while keeping the user's chosen language.

中文简介正在准备中。当前显示英语简介。

  • Reading concise replies in a terminal
  • Getting conclusions before explanations
  • Reducing wording while keeping technical details
JuliusBrussee/caveman11.4万2026年10月18日 更新

Create short commit messages using Conventional Commits, a format that labels the type of change. Emphasize intent, keep the subject concise, and include explanatory text when breaking changes, security fixes, data migrations, or reversions require context.

中文简介正在准备中。当前显示英语简介。

  • Writing a commit message for code changes
  • Standardizing commit message format
  • Documenting breaking changes and migration steps
JuliusBrussee/caveman11.4万2026年10月18日 更新

Compress memory files and task lists into shorter wording to reduce input tokens. Keeps code and document structure intact, saves a readable backup separately, and sends the text to the configured model provider.

中文简介正在准备中。当前显示英语简介。

  • Shortening CLAUDE.md to reduce input tokens
  • Compressing task lists and preference files
  • Keeping readable backups of compressed files
JuliusBrussee/caveman11.4万2026年10月18日 更新

Find LLM workflows in a codebase and label them by the job they perform, so Caveman Cloud can separate spending by workflow. Present a labeling proposal for approval, apply focused code changes, and check an affected execution path.

中文简介正在准备中。当前显示英语简介。

  • Breaking down LLM spending by job
  • Inventorying LLM use in APIs, scheduled jobs, and scripts
  • Separating evaluation spending from other workflows
JuliusBrussee/caveman11.4万2026年10月18日 更新

Review Caveman Cloud spending, latency, errors, and potential improvements using current reports and traces, or individual execution records. Produce findings tied to time windows and trace IDs, while keeping measured costs, estimated opportunities, and verified savings separate.

中文简介正在准备中。当前显示英语简介。

  • Understanding which workflows drive LLM spending
  • Investigating slow responses and errors
  • Reviewing measured costs and verified savings separately
JuliusBrussee/caveman11.4万2026年10月18日 更新

查看 JuliusBrussee 的全部技能

报告此技能的问题