old-lint

Inspect source code change diffs for quality issues.

37|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/jpcaparas/skills --skill old-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: old-lint
Source: https://github.com/jpcaparas/skills/tree/main/skills/skill-creator-advanced/evals/files/retirement-library/skills/stable/old-lint
Command: npx skills add https://github.com/jpcaparas/skills --skill old-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Old Lint provides a review of source changes for quality problems, identifying potential issues in code that could be superseded by code-review.

Core Features & Use Cases

  • Code Quality Review: Inspect diff outputs for quality problems in source code.
  • Legacy Use Case: This Skill serves as a reference for historical code review processes and could be replaced by code-review for newer systems.

Quick Start

To run the old-lint skill on a set of source code changes, you can execute 'old-lint my-source-code-change.patch'.

Frequently Asked Questions about old-lint

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

FAQPage Schema
How do I automate source code quality review on a patch file?

To automate source code quality review, you can execute the 'old-lint' script directly on a source code change file, passing the patch file as an argument to analyze the diff for issues.

What is the difference between legacy code review and modern source code review practices?

Legacy code review analyzes source changes using an outdated method that may not reflect current standards, whereas modern practices likely offer more comprehensive and up-to-date code quality insights.

Can I use this tool to inspect diff outputs for quality problems?

Yes, you can inspect diff outputs for quality problems by running the script on your source code change files, which analyzes the provided patches to identify potential issues.

Are there limitations to using an outdated code quality review method?

The primary limitation of this outdated code quality review method is that its insights may be superseded by newer code review practices, making it more suitable as a historical reference than a primary tool.

When should I use a legacy code review tool instead of a newer code review skill?

A legacy code review tool should be used when you need a reference for historical code review processes or when maintaining systems specifically designed around older source code analysis methods.

Does old-lint require any dependencies to process source code changes?

No, old-lint does not require any dependencies to process source code changes, allowing you to directly execute the included scripts on your patch files without additional environment setup.