fabric-x-committer

Conventions for writing NEW Go code in the Fabric-X Committer repo: code organization/ordering, concurrency (errgroup + context-aware channels), Go 1.26 idioms, error handling, logging, and service/config/metrics structure. Use this skill BEFORE writing or modifying any Go source in this repository — adding a service, component, function, gRPC handler, or config field, or refactoring existing code — so the new code matches established patterns and passes `make lint`. For test-only work use the `tests` skill; for reviewing a PR use `pr-review`.

Audit the repository's documentation, agent instructions, other skills, config samples, and config templates for staleness introduced by a code change — every *.md, *.yaml/*.yml, and *.tmpl file. Use AFTER finishing any development task that touched Go code, config fields, CLI flags, metrics, make targets, scripts, or file/package layout, and whenever the user asks to "check the docs", "audit the docs", or "did I make anything obsolete?". It auto-fixes the repo's generated docs (metrics reference, CLI help, loadgen sample tree) and reports likely-stale prose, agent instructions, skills, and config templates with file:line and a suggested edit. Runs well on a dispatched subagent to keep the parent context clean. It only audits EXISTING files for staleness a code change introduced — do not use it to author or edit documentation (writing a new doc, adding a section, rewriting prose). For writing new Go code use the `development` skill; for tests use `tests`; for PR review use `pr-review`.

Review a GitHub pull request for the Fabric-X Committer project and post comment-only findings. Invoke with the PR URL.

Write and/or run unit and integration tests, ensuring high code coverage and reliability.

Write a commit message (which becomes the GitHub PR description verbatim) or open a GitHub issue for the Fabric-X Committer repo, following the repo's PR template and conventions. Use whenever the user wants to commit staged changes, write or fix a commit/PR message, prepare a PR description, or open/file/create a GitHub issue for this project — even for terse asks like "commit this", "write the PR description", or "file an issue for this bug".