ij-perf-report-aggregator
AGENTS.md24 starsChanged 5 days agoApache-2.0View on GitHub
IJ Perf collects performance reports from TeamCity, stores them in ClickHouse, detects degradations and visualizes the results. Format TypeScript/Vue/JS/Markdown with oxfmt (config: .oxfmtrc.json); never run prettier — it is not a dependency, and npx prettier pulls a version that rewraps whole files. Pass paths with a ./ prefix: bare relative paths can fail with "Expected at least one target file". make lint runs the full set (also oxfmt --check, knip and deadcode).
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-dashboard-categorySkill
- add-dashboard-pageSkill
- clickhouse-updateSkill
- review-ij-perfSkill
The file
Files
Project
IJ Perf collects performance reports from TeamCity, stores them in ClickHouse, detects degradations and visualizes the results.
cmd/,pkg/— Go services and libraries (backend,tc-collector,degradation-detector, …).dashboard/new-dashboard/— Vue 3 + TypeScript dashboard (pnpm, Vite); pages live insrc/components, routes insrc/routes.ts.db-schema/,deployment/— ClickHouse schemas and deployment configs..agents/skills/— step-by-step guides for recurring tasks (adding a dashboard category or page, updating ClickHouse).
Formatting
Format TypeScript/Vue/JS/Markdown with oxfmt (config: .oxfmtrc.json); never run prettier — it is not a dependency, and npx prettier pulls a version that rewraps whole files.
node_modules/.bin/oxfmt ./dashboard/new-dashboard/src/routes.tsPass paths with a ./ prefix: bare relative paths can fail with "Expected at least one target file".
Checks
Dashboard:
pnpm vue-tsc --noEmit -p dashboard/new-dashboard
pnpm lint
pnpm testGo:
go test ./cmd/... ./pkg/...
golangci-lint run cmd/... pkg/...make lint runs the full set (also oxfmt --check, knip and deadcode).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

