skills.rest
kelsi-andrewss
kelsi-andrewssCOMMUNITY
Explore all skills by this author →
GitHub

lint

Automates lint checks for npm-based projects and reports PASS, FAIL, or WARN outcomes.

1|Updated Feb 21, 2026
Search Tags:#automation#npm#worktree#code-quality#lint#node#pre-merge
One-click install
npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill lint-kelsi-andrewss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/kelsi-andrewss/claude-multi-agent-pipeline/tree/main/skills/lint
Command: npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill lint-kelsi-andrewss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce code quality by automating lint checks before merging work.

Core Features & Use Cases

  • Detects if a linter is configured in the target worktree's package.json and provides skip behavior if not.
  • Executes an npm lint workflow when a linter is configured, using the worktree path as the prefix.
  • Reports results with clear messaging: pass, fail, or warnings, enabling fast corrective actions.

Quick Start

Ask Claude to lint the current story worktree to verify the codebase has no lint errors before merging.

Frequently Asked Questions about lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pre-merge lint checks for a Node.js worktree?▼

It automates pre-merge lint checks by detecting a configured linter in package.json and executing npm run lint within the worktree to enforce code quality before merging.

What happens if there is no linter configured in package.json?▼

If no linter is configured in package.json, the Skill provides skip behavior and does not execute npm run lint, allowing the pre-merge workflow to proceed without lint errors.

Can I run lint checks on a specific story ID instead of the current worktree?▼

Yes, you can run lint checks on a specific story ID or the current worktree. The Skill applies the lint workflow to the specified worktree path prefix when executing npm run lint.

How are lint errors and warnings reported before a code merge?▼

Lint results are reported with clear pass, warn, or fail messaging semantics, enabling fast corrective actions by highlighting code quality issues before merging.

Does this pre-merge lint automation work outside of npm and Node environments?▼

No, this automation specifically targets Node environments by validating the linter configuration within package.json and executing the npm run lint command to analyze code quality.

Related Skills

Explore More Software Engineering Skills→
hopeoverturehopeoverture
6

eslint-prettier-husky-config

Configure ESLint v9, Prettier, Husky, and lint-staged for Next.js projects.

Community
Advanced
cedricfarinazzocedricfarinazzo

merge-update-pr

Rebase a PR branch on main and push only when a merge commit is created.

Community
Advanced
holger1411holger1411
70

qa

Run lint, format, TypeScript, and build checks on AstroDeck projects.

Community
Advanced
yckkkkyckkkk
1

health

Aggregate code quality tool outputs into a weighted 0-10 health score and trend report.

Community
Advanced