lint

Analyze git-staged files for documentation drift and spelling errors in Pegasus WMS projects.

Updated Feb 13, 2026

Search Tags:#static analysis #code review #linting #documentation #semantic #pegasus

Ready to run

npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill lint-pegasus-isi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/pegasus-isi/claude-plugin-marketplace/tree/main/plugins/pegasus-dev/skills/lint
Command: npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill lint-pegasus-isi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codespell, and includes scripts (resource) components.

What problem does it solve?

This skill addresses the gap between mechanical code formatters and human-level code quality by identifying semantic defects like stale documentation, comment-code drift, and inconsistent terminology that static analysis tools miss.

Core Features & Use Cases

Semantic Review: Detects docstring-signature mismatches, stale TODOs, and misleading variable names.
Mechanical Cleanup: Identifies spelling errors and outdated string formatting (e.g., .format() to f-strings) with optional safe-fix application.
Use Case: Use this during a code review to ensure that your documentation and comments accurately reflect the logic changes made in your latest commit.

Quick Start

Run the lint skill to scan your currently staged git changes for semantic issues and spelling errors.

Frequently Asked Questions about lint

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

FAQPage Schema

How do I check staged git changes for stale documentation and spelling errors?▼

To check staged git changes for semantic issues, run a linting scan over your currently staged files to identify stale documentation, comment-code drift, and spelling errors.

What is semantic code analysis and how does it find documentation drift?▼

Semantic code analysis identifies documentation drift by using custom shell-based scanning and LLM-driven review to detect logical mismatches between code signatures, docstrings, and comments that static analysis tools miss.

How do I detect outdated string formatting and non-idiomatic code patterns?▼

You detect outdated string formatting and non-idiomatic code patterns by running semantic linting on your git-staged files, which flags outdated syntax like .format() usage for f-string conversion and other house-style deviations.

Does this linting tool work with Pegasus WMS projects?▼

Yes, this linting tool is specifically designed for Pegasus WMS projects, utilizing custom shell-based scanning and LLM-driven review to enforce high-quality code and documentation standards within that environment.

Can I use codespell to fix spelling errors in my code review?▼

You can use codespell integration during your code review to identify spelling errors across your git-staged files, with the semantic linting process providing optional safe-fix application for mechanical cleanup.