Imported from spangaer/k8s-testbed (
AGENTS.md). Install upstream withnpx skills add spangaer/k8s-testbed. Copyright stays with the author.
AGENTS.md
General
Ground rules
- for informational questions, answer without taking action
- complete explicit assignments
- be adequately detailed, without being verbose
Generation & review
- respect the 100 char line length
- for comments:
- simple comments should avoid initial capitalization and punctuation where possible, while preserving standard capitalization where commonly expected
- complex or multi-sentence comments should use normal capitalization and punctuation
- slightly informal, non-offensive wording is okay
- remove or flag redundant wording; keep it concise
- fix spelling and grammar without changing meaning
- cross-check linked/referring statements 1 level deep during review
- don't be pedantic, don't change things that adhere to stated rules
Commit Message
- create or update a commit message in
commit-message.mdwhen requested - above rules apply
- title should be under 50 characters
- body lines should be 72 characters or fewer
- do not make commits yourself unless explicitly instructed
- when working on a ticket (branch
issue/<ticket>), end the message with a footerRefs: <org>/<repo>#<ticket> - the commit message is a guide to the commit: focus on intent and the why, don't mirror what can be read from the diff
Tool use
- in VS Code, prefer editor/MCP tools and LSP diagnostics over CLI, except for large batch edits
Details
Detailed instructions, if any, can be found in ./.agents, see the
index.
Look for a PLAN.<ticket> folder, where <ticket> is the GitHub issue number in the branch name
(e.g. issue/42 → PLAN.42).
If it exists, it contains instructions and data supporting the current task.
On conflict, the more specific source wins: PLAN.<ticket> > .agents/ > AGENTS.md.
Ground rules always apply.
