How do I install the Run Tests And Linters skill?

Run npx skillmds@latest add lorem-dev/run-tests-and-linters in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Run Tests And Linters safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Run Tests And Linters?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Run Tests And Linters free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Run Tests And Linters?

lorem-dev (@lorem-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Run Tests And Linters by lorem-dev — Agent Skill

Name: Run Tests And Linters
Author: lorem-dev

Run Tests And Linters

Install dependencies, run the Rust gates (cargo fmt, clippy, test) and the TypeScript gates (ESLint, tsc typecheck, Vitest with v8 coverage at 90%, and the renderer Vite build). Report any failures clearly with file paths and line numbers.

lorem-dev fc82363 2.9 KB Updated Sep 17, 2026

File contents

run-tests-and-linters

Run the full quality gate for SkillKeeper. The project is a Rust workspace (crates + the Tauri backend) plus a small TypeScript surface (the renderer and the packages/i18n catalogs), so the gate has both a Rust half and a TypeScript half.

Steps

Ensure dependencies are installed.
```
pnpm install
```
The stable Rust toolchain is pinned in rust-toolchain.toml and installed by rustup on first cargo invocation. If pnpm install fails, report the error and stop -- later steps will not produce meaningful results.
Run the Rust gates.
```
cargo fmt --all --check                              # formatting
cargo clippy --workspace --all-targets -- -D warnings # lints; warnings fail (matches CI)
cargo test --workspace                               # tests; also regenerates the ts-rs bindings
```
Any cargo fmt --check diff, clippy warning, or failed test is a blocker. Report each with its crate, file path, and line number. Note that cargo test regenerates the TypeScript bindings under apps/desktop/src/renderer/services/bridge/generated/; if that leaves a dirty working tree, the bindings were stale and must be committed.
Run ESLint.
```
pnpm lint
```
Collect any errors or warnings. ESLint errors are blockers; warnings should be reported but are not blocking unless the lint script is configured to treat them as errors.
Run TypeScript typecheck.
```
pnpm typecheck
```
Any type error is a blocker. Report each error with its file path and line number.
Run tests with coverage.
```
pnpm test:cov
```
The Vitest v8 coverage gate requires 90% lines and 90% branches; it is scoped to packages/i18n (see vitest.config.ts). If the gate fails:
- Show the coverage summary table.
- Identify which files are below threshold.
- Clearly state that the coverage gate is blocking the release.

Build the renderer.

pnpm --filter @skillkeeper/desktop frontend:build   # vite build

A failed frontend build is a blocker.

Report. Produce a structured summary:

cargo fmt:   PASS / FAIL
cargo clippy: PASS / FAIL (N warnings)
cargo test:  PASS / FAIL (N failed, N passed)
lint:        PASS / FAIL (N errors, N warnings)
typecheck:   PASS / FAIL (N errors)
tests:       PASS / FAIL (N failed, N passed)
coverage:    PASS / FAIL (lines X%, branches X% -- threshold 90%)
frontend:    PASS / FAIL

Overall: PASS / FAIL

For each failure include the relevant output excerpt so the developer can act on it immediately.

---name: run-tests-and-lintersdescription: Install dependencies, run the Rust gates (cargo fmt, clippy, test) and the TypeScript gates (ESLint, tsc typecheck, Vitest with v8 coverage at 90%, and the renderer Vite build). Report any failures clearly with file paths and line numbers.---# run-tests-and-lintersRun the full quality gate for SkillKeeper. The project is a Rust workspace(crates + the Tauri backend) plus a small TypeScript surface (the renderer andthe `packages/i18n` catalogs), so the gate has both a Rust half and aTypeScript half.## Steps1. **Ensure dependencies are installed.** ```bash pnpm install ``` The stable Rust toolchain is pinned in `rust-toolchain.toml` and installed by rustup on first `cargo` invocation. If `pnpm install` fails, report the error and stop -- later steps will not produce meaningful results.2. **Run the Rust gates.** ```bash cargo fmt --all --check # formatting cargo clippy --workspace --all-targets -- -D warnings # lints; warnings fail (matches CI) cargo test --workspace # tests; also regenerates the ts-rs bindings ``` Any `cargo fmt --check` diff, clippy warning, or failed test is a blocker. Report each with its crate, file path, and line number. Note that `cargo test` regenerates the TypeScript bindings under `apps/desktop/src/renderer/services/bridge/generated/`; if that leaves a dirty working tree, the bindings were stale and must be committed.3. **Run ESLint.** ```bash pnpm lint ``` Collect any errors or warnings. ESLint errors are blockers; warnings should be reported but are not blocking unless the lint script is configured to treat them as errors.4. **Run TypeScript typecheck.** ```bash pnpm typecheck ``` Any type error is a blocker. Report each error with its file path and line number.5. **Run tests with coverage.** ```bash pnpm test:cov ``` The Vitest v8 coverage gate requires 90% lines and 90% branches; it is scoped to `packages/i18n` (see `vitest.config.ts`). If the gate fails: - Show the coverage summary table. - Identify which files are below threshold. - Clearly state that the coverage gate is blocking the release.6. **Build the renderer.** ```bash pnpm --filter @skillkeeper/desktop frontend:build # vite build ``` A failed frontend build is a blocker.7. **Report.** Produce a structured summary: ``` cargo fmt: PASS / FAIL cargo clippy: PASS / FAIL (N warnings) cargo test: PASS / FAIL (N failed, N passed) lint: PASS / FAIL (N errors, N warnings) typecheck: PASS / FAIL (N errors) tests: PASS / FAIL (N failed, N passed) coverage: PASS / FAIL (lines X%, branches X% -- threshold 90%) frontend: PASS / FAIL Overall: PASS / FAIL ``` For each failure include the relevant output excerpt so the developer can act on it immediately.

Frequently asked questions