Skip to content

dirien/yet-another-agent-harness / .claude/skills/lint-fix

lint-fix

Verified

Detect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.

FileKindSize
SKILL.mdskill md5.2 KB
references/fix-protocol.mdmarkdown2.2 KB
references/tool-detection.mdmarkdown3.0 KB

references/tool-detection.md

View on GitHub
<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Tool detection

Detect project linting, formatting, and validation tools by scanning
for configuration files, Makefile targets, and package manager scripts.
Use the first match found in each ecosystem.

## Makefile detection

If `Makefile` exists, discover relevant targets:

```bash
make -qp 2>/dev/null | grep -E '^[a-z].*:' | cut -d: -f1 | sort -u
```

Look for these common targets: `lint`, `test`, `validate`, `format`,
`fmt`, `gen`, `generate`, `build`, `check`, `vet`.

## Node.js / TypeScript

If `package.json` exists:

```bash
jq -r '.scripts | keys[]' package.json 2>/dev/null
```

Common scripts: `lint`, `test`, `format`, `prettier`, `eslint`,
`build`, `typecheck`, `validate`.

Standalone configs (check existence):

- `.eslintrc*`, `eslint.config.*` → `npx eslint .`
- `.prettierrc*`, `prettier.config.*` → `npx prettier --check .`
- `biome.json`, `biome.jsonc` → `npx biome check .`
- `tsconfig.json` → `npx tsc --noEmit`
- `.stylelintrc*` → `npx stylelint "**/*.css"`

## Go

If `go.mod` exists:

- `golangci-lint run` (if `golangci-lint` installed or
  `.golangci.yml` exists)
- `gofmt -s -l .` (always available with Go)
- `go vet ./...` (always available with Go)
- `go test ./...` (always available with Go)
- `go build ./...` (always available with Go)

## Python

If `pyproject.toml`, `setup.py`, or `requirements.txt` exists:

- `ruff check .` (if `ruff` installed or `[tool.ruff]` in
  pyproject.toml)
- `black --check .` (if `black` installed or `[tool.black]` in
  pyproject.toml)
- `flake8` (if `flake8` installed or `.flake8` exists)
- `mypy .` (if `mypy` installed or `[tool.mypy]` in pyproject.toml)
- `pytest` (if `pytest` installed or `[tool.pytest]` in
  pyproject.toml)

## .NET

If `*.csproj` or `*.sln` exists:

- `dotnet format --verify-no-changes`
- `dotnet build`
- `dotnet test`

## Rust

If `Cargo.toml` exists:

- `cargo clippy -- -D warnings`
- `cargo fmt --check`
- `cargo test`
- `cargo build`

## Markdown (always check)

- `markdownlint` (if installed or `.markdownlint*` config exists)
- `commitlint` (if installed or `.commitlintrc*` config exists)

## Pipeline ordering

Once tools are detected, order them:

1. **Generation** — `make gen`, code generators (must run first,
   output may overwrite manual fixes)
2. **Formatting** — prettier, black, gofmt, rustfmt, dotnet format
   (fix formatting before linting)
3. **Linting** — eslint, golangci-lint, ruff, clippy, markdownlint
4. **Type checking** — tsc, mypy (after lint fixes)
5. **Validation** — `make validate`, schema checks
6. **Testing** — go test, pytest, jest, cargo test, dotnet test
7. **Building** — go build, cargo build, dotnet build (final check)

## Fallback

If no tools are detected, report to the user:

```text
No linting or validation tools detected in this project.

Checked: Makefile, package.json, go.mod, pyproject.toml,
*.csproj, Cargo.toml, standalone linter configs.

Would you like to set up linting for this project?
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall