Best use case
lint-build-test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
How to check code by linting, building, and testing.
Teams using lint-build-test should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lint-build-test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lint-build-test Compares
| Feature / Agent | lint-build-test | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
How to check code by linting, building, and testing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
When asked to check, lint, build, or test code, follow these steps: ## 1. Analyze changed files First, check which files have changed using `git status` or `git diff --name-only`. Categorize the changes: - **Source files**: `.ts`, `.js`, `.mts`, `.mjs`, `.cjs`, `.cts`, `.tsx`, `.jsx` - **Meta files**: `.md`, `.yml`, `.yaml`, `.json`, `.html` ## 2. Determine what to run Based on the changed files: - **No files changed**: Nothing to do. - **Only meta files changed**: Run only `yarn lint:misc --write` (or `yarn workspace <package-name> lint:misc --write` for a specific package). - **Source files changed**: Run the full check (see below). ## 3. Run the full check (if needed) ### For a specific package If a package name is specified (e.g. `@metamask/ocap-kernel`): 1. `yarn workspace <package-name> lint:fix` 2. `yarn workspace <package-name> build` 3. `yarn workspace <package-name> test:dev:quiet` ### For the entire monorepo If no package is specified: 1. `yarn lint:fix` 2. `yarn build` 3. `yarn test:dev:quiet` Report any errors encountered during these steps.
Related Skills
wallet
Use the wallet tools for all balance, send, and sign operations. Supports both ETH and ERC-20 tokens. The away wallet operates autonomously after setup — the home device does not need to be online.
metamask
Use the MetaMask tools to request and interact with wallet capabilities from the MetaMask capability vendor.
discovery
Use the discovery tools to find and use services through a service matcher. Do not rely on prior knowledge of services, providers, or APIs.
update-changelogs
Updates changelogs for all packages with consumer-facing changes.
push
Pushes the current branch to the remote repository.
pr
Creates a pull request for the current branch.
glossary
How to add entries to the glossary
evm-wallet-docker-e2e
Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures).
create-package
Create a new monorepo package using the create-package CLI
commit
Optionally checks, then commits code to the current or a new feature branch.
code-review
How to review code; a pull request, feature branch, local changes etc.
team-builder
用于组合和派遣并行团队的交互式代理选择器