compiling
- Repo stars 340
- License Apache-2.0
- Author updated Live
- Author repo skywalking-banyandb
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @apache · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: compiling
description: Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or…
category: engineering
runtime: no special runtime
---
# compiling output preview
## PART A: Task fit
- Use case: Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this project. Follow these steps to compile the project. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Step 1: Generate protobuf and mock code / Step 2: Build all binaries / Troubleshooting” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this project. Follow these steps to compile the project. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Step 1: Generate protobuf and mock code / Step 2: Build all binaries / Troubleshooting” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Step 1: Generate protobuf and mock code / Step 2: Build all binaries / Troubleshooting”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: compiling
description: Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or…
category: engineering
source: apache/skywalking-banyandb
---
# compiling
## When to use
- Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Step 1: Generate protobuf and mock code / Step 2: Build all binaries / Troubleshooting” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "compiling" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Step 1: Generate protobuf and mock code / Step 2: Build all binaries / Troubleshooting
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Compiling SkyWalking BanyanDB
Follow these steps to compile the project.
Step 1: Generate protobuf and mock code
Run make generate first. This regenerates .pb.go files from .proto definitions and mock files via mockgen.
This step is required whenever:
- Proto files (
.proto) have been added or modified - Go interfaces used by mockgen have changed
If generate fails, check:
protocand Go protobuf plugins are installed- Proto file syntax is valid
- Interface signatures match mock expectations
Step 2: Build all binaries
Run make build to compile all project components: ui, banyand, bydbctl, mcp, fodc/agent, fodc/proxy.
Binaries are output to each component's build/bin/dev/ directory.
Troubleshooting
- Missing fields in .pb.go: Proto files were updated but
make generatewas not run. Run it first. - Mock generation failures: An interface changed but the mock wasn't regenerated.
make generatefixes this. - Import errors: Check import aliases match CLAUDE.md conventions (e.g.,
commonv1,databasev1).
Other useful targets
make clean— clean all build artifactsmake clean-build— clean only build binariesmake lint— run lintersmake test— run tests
Decide Fit First
Design Intent
How To Use It
Boundaries And Review