lint-rule-gen

You can automate code review feedback by generating custom ESLint rules from recurring anti-patterns found in Git history and review diffs. This allows you to automatically enforce code quality standards instead of manually raising the same issues.

Yes, you can generate lint rules for JavaScript and TypeScript projects from a single pattern description. The system automatically creates rules for ESLint or agent and Guardian configurations to dynamically check your codebase.

You can extract recurring anti-patterns by analyzing Git history and code review diffs. The system identifies repeated issues, such as console.log usage, and derives validation steps to install new lint rules into your project's configuration files.

Yes, generating and applying custom lint rules requires access to git history, diffs, and local CLAUDE config files. This access is necessary to derive, validate, and install the new rules into the target project's ESLint configuration.

The best way to stop repetitive code review comments is to convert review feedback patterns into automated lint rules. By targeting JavaScript and TypeScript codebases, you can generate rules that warn or error on specific anti-patterns automatically.

You can generate rules for ESLint (.eslintrc.json), agent rules, and Guardian rules for dynamic code checks. These configurations are automatically generated from extracted feedback patterns to enforce code quality across your project.