Skip to content

GravionLabs/elysion / .agents/skills/implementation

implementation

Verified

Rules for code changes: every change ships with tests, dispatches to <lang>-implementation. Use for implement, write code, add feature, test requests.

references/lint.md

View on GitHub
# Lint changed files

`scripts/Format-Changed.ps1 -Lint` runs the linter on the changed files. It is the `-Lint` mode of the format runner: same file selection (`-Base`, extension grouping without `-Language`), same `{files}` handling, same `-WhatIf`. Lint is read-only and never combined with `-Check`.

```powershell
pwsh scripts/Format-Changed.ps1 -Lint                  # detect the languages from the changed files
pwsh scripts/Format-Changed.ps1 -Lint -Language py
pwsh scripts/Format-Changed.ps1 -Lint -Language ts -Base origin/release/next
```

Defaults (no `lint` key): ts eslint (`npx biome lint --no-errors-on-unmatched {files}` in a Biome project), ng eslint, py `uv run ruff check {files}`, dotnet `dotnet format analyzers --verify-no-changes --include {files}`, rust `cargo clippy --all-targets -- -D warnings` (whole crate, no `{files}`), go `golangci-lint run {files}`. A tool that is missing or whose probe fails is `skipped: <tool> not configured`.

Override (`.agents/config.json`, key `lint`, schema `schema/config.schema.json`):

```json
{
  "lint": {
    "dotnet": {
      "extensions": [".cs"],
      "command": ["jb inspectcode MySolution.sln --no-build --include={files} -o=obj/inspect.sarif"]
    }
  }
}
```

- `lint: false` disables: `skipped: disabled`, exit 0.
- `command` is a string or an array run in order, the first non-zero exit stops the run and is the exit code. `extensions` absent: those of the built-in default of the language.
- In lint mode a command without `{files}` runs as it is; no files are appended.
- A configured tool that is missing is an error. A missing `command` key is an error.
- Success prints `linted: <n> files`.

`jb inspectcode` writes SARIF (`-o`, `--no-build`); whether it exits non-zero on findings is not verified here: when it does not, a second command in the array must fail on the report, or `code-review` reads the SARIF.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall