code-qualitylisted

# Code Quality Skill Use this skill for code hygiene, quality gates, and pre-commit workflows. **Trigger keywords:** code quality, lint, type checking, pre-commit, build, fix errors, quality gate ## Work Item Attribution Quality gate runs should be attributed. Before fixing errors: 1. Ensure a feature or bug is active: `wipnote status` 2. If fixing a bug: `wipnote bug create "Fix: description" --track <trk-id>` then `wipnote bug start <id>` 3. Run `wipnote help` for available commands --- ## Quality Gate Pattern: BUILD → LINT → TEST Every project enforces the same three-phase pattern. Only commit when all three pass. ### Step 1: Detect Project Type Check for a project manifest in the repository root: | File | Language/Runtime | |------|-----------------| | `go.mod` | Go | | `package.json` | JavaScript / TypeScript (Node) | | `pyproject.toml` or `requirements.txt` | Python | | `Cargo.toml` | Rust | | `pom.xml` or `build.gradle` | Java / JVM | Multiple manifests may coexist (e.g., a Go backend with a `package.json` frontend) — run quality gates for each. ### Step 2: Run the Three Phases #### Go (`go.mod`) ```bash go build ./... # BUILD — type checking + compilation go vet ./... # LINT — static analysis go test ./... # TEST — run test suite ``` #### JavaScript / TypeScript (`package.json`) ```bash npm run build # BUILD — or tsc --noEmit for type-check only npm run lint # LINT — eslint, biome, or equivalen