Code guidance for elastic/integrations
This repo has companion Claude Code skills in [`elastic/integration-skills`](https://github.com/elastic/integration-skills) that cover building, reviewing, and maintaining Elastic integration packages.
If the skills aren
work, designing
analyses, pre-registering predictions, running reproducible analyses, investigating
anomalies, verifying results, and reviewing them adversarially.
The architecture is reused from [Superpowers](https://github.com/obra/superpowers): a
session-start bootstrap
release flow breaks the sync. Rebase onto the current default branch before asking for review — a stale base shows up as dozens of unrelated "changed" files.
- Package versions (`VersionPrefix`, `.release-please-manifest.json
integration. The tool creates safe sandboxed environments where Claude can execute commands and make code changes without affecting the host system.
## Common Development Commands
### Build and Development
- `npm run build
driver scripts in `scripts/burp/`, host setup in `setup/burp/`), and the standalone `wiki/`, `research/`, `disclosure/`, `code-review/`. They load on demand via the Skill tool (descriptions in the `/skills` picker), discovered
networks)
- Disabled skills: browser, canvas, nodes, screen
## Memory Preservation (CRITICAL)
> **RULE: App updates and code changes MUST NEVER affect user memory.**
The agent's memory is sacred. These files live
calling the evaluator.
## Pre-PR Checklist
If you use Claude Code, run `/simplify` before creating a pull request to review changed files for clarity, consistency, and maintainability improvements. Apply
capability to the Claude Code plugin, mirror it for Codex and **Hermes** (`plugins/`); those parity gaps have been flagged.
- **On PR/spec reviews, trust only what you read** — don't pass
same Skill files directly without the Harness.
Direct runs remain user reviewed.
Harness and CI runs enforce strict output checks.
## Architecture
- `crates/skilld-core`: shared Rust domain types and Agent target rules
validates dependencies and computes execution tiers. The version-3 controller runs
one fresh Claude Code process per worker, sequentially, with explicit inputs and
per-attempt outputs. It stops on unavailable
same human, and cross-surface funnels silently stop joining — the failure is invisible in codereview and only shows up as wrong numbers.
- Authenticated API requests get this for free
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.