Resolve residual Biome lint findings on changed feature branch files.
npx skills add https://github.com/farzanmrz/beat-radar-agent --skill feature-lint
Please help me install this Agent Skill. Skill: feature-lint Source: https://github.com/farzanmrz/beat-radar-agent/tree/main/.claude/skills/feature-lint Command: npx skills add https://github.com/farzanmrz/beat-radar-agent --skill feature-lint
This Skill resolves the remaining Biome lint findings on a feature branch after safe auto-fixes have already been applied, focusing on issues that require human-style edits and careful judgment.
Use the feature-lint skill to clean up residual Biome findings on my current branch against main.
High-intent search queries and answers about installing and using this skill.
To fix residual Biome lint findings on changed TypeScript files, apply risk-tiered manual edits to the specific issues that cannot be safely auto-fixed, then validate with a build step. This workflow targets behavior-changing rules requiring human-style judgment.
Clean up lint findings on a feature branch by scoping corrections to only files changed from a chosen base ref. This diff scoping prevents scope creep into untouched TypeScript, JSX, and JavaScript code.
The best way to handle manual Biome lint corrections is using a risk-aware workflow that separates low-risk mechanical fixes from higher-risk semantic changes like hook dependency issues, ensuring behavior-changing edits are flagged for review-worthy visibility.
Yes, residual lint cleanup works with Next.js and TypeScript by using a TypeScript or Next build as the final build-gated verification step before reporting results, ensuring branch correctness is preserved.
Diff scoping is necessary when resolving lint findings on a feature branch because it restricts manual corrections to modified files, avoiding scope creep and preserving the correctness of untouched code.
TuiennLint and format React projects with ESLint and Prettier.
GolferGeekRun npm lint, format, test, and build before commits.
AkbarDevopIdentify production-risk findings in a code diff before merging.
twiced-technology-gmbhDiagnose project environments and configure linters for JavaScript, TypeScript, Python, Java, Rust, and Go.
