repo-fact
Use when asked for this repository's registered fact or codeword. Loads the canonical answer format.
- License 许可
- Apache-2.0
- 所属仓库
- stacklok/mecatl
- 最近更新
- 2026-11-15
- Stars
- ★ 309
- Forks
- 29
01 前言 Front Matter
- name
- repo-fact
- description
- Use when asked for this repository's registered fact or codeword. Loads the canonical answer format.
03 SKILL.md 正文
The repository fact
When asked for this repository's registered fact, reply with exactly one line:
REPO-FACT quetzal-7
04 同仓库更多 Skills
greet
Use when asked to greet someone with the ceremonial mecatl greeting. Loads the exact greeting format.
go-table-tests
Write idiomatic table-driven Go tests that stay offline and follow this repo's conventions.
commit-style
Write Conventional-Commits messages for this repo, with the required Co-Authored-By trailer.
tech-writer
Use when writing or substantively editing user-facing documentation: drafting a new page, rewriting or restructuring an existing one, adding a major section, or turning engineering material (PR descriptions, specs, release notes, rough notes) into docs. Writes clear, focused technical documentation following the Diataxis framework and Mecatl's canonical style guide. Use it even when the request doesn't mention writing quality; it governs how documentation gets written. Not for editorial review of finished work.
perf-optimization
Profile-driven performance optimization of mecatl using the offline benchmark + scenario harness. Use when optimizing allocations or latency, reducing allocs/op or memory, profiling a Go benchmark, pinpointing a hotspot with pprof, proving a win with benchstat, adding a regression benchmark, wiring profile-guided optimization (PGO), or investigating "why is this slow / allocating" or a suspected perf regression. Covers task bench, task perf:scenarios, memprofile -> pprof, benchstat A/B, allocs-first gating, PGO setup, and the discipline (follow the profile not the hypothesis; keep pure-perf changes byte-identical; mutation-test cache guards; skip the wrong abstraction). NOT for the live perf MCP server (use perf-mcp-interpretation) or non-mecatl Go profiling.
perf-mcp-interpretation
Interpret the mecatl perf MCP server's output to diagnose latency, goroutine leaks, GC pressure, allocation churn, and memory growth in a running mecatl harness. Use when connected to the mecatl perf MCP server (the perf:// resources or the query_metric / top_cpu_functions / capture_cpu_profile / top_allocations / list_slow_turns / capture_flight_recorder tools) and investigating why mecatl is slow, leaking, or growing. Covers tool routing/cost, reading pprof rankings and runtime metrics, and the leak/contention/GC signatures. NOT for generic Go profiling or non-mecatl MCP servers.