lint-kit

Lints kit files for missing platform prefixes and reports severity-coded findings.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill lint-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-kit
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/lint-kit
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill lint-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-specific content is scattered across universal kit files, risking drift and broken cross-platform behavior. This Skill audits kit contents to surface any content that should be in a platform-prefixed file and ensures consistency with the kit's naming conventions.

Core Features & Use Cases

  • Audits kit files (kit/.md, kit/skills/<name>/SKILL.md) and bootstrap/.template to identify platform drift.
  • Reports findings with severities, guiding maintainers to relocate content to ios-, web-, etc.
  • Integrates with bin/lint to provide a deterministic, read-only check that exits non-zero on HIGH findings.

Quick Start

Run the lint-kit skill to scan universal kit files for platform-prefix drift and generate a severity report.

Frequently Asked Questions about lint-kit

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

FAQPage Schema
What is platform-prefix drift in universal kit files?

Platform drift happens when platform-specific content is scattered across universal kit files, risking broken behavior. It occurs when content meant for platform-prefixed files like ios-* or web-* appears in neutral kit paths.

How do I lint kit files for platform drift?

Run the lint check to scan kit/*.md, kit/skills/<name>/SKILL.md, and bootstrap/*.template files. It reads universal references and generates a severity-coded report, exiting non-zero when HIGH findings exist.

Does the kit linter require bin/lint to function?

Yes, the kit linter requires bin/lint to provide a deterministic, read-only check. It operates within the kit scope, reading only platform-neutral references to identify naming convention violations.

Can I use this linter to check bootstrap template files?

Yes, you can lint bootstrap/*.template files to identify platform drift. The linter audits these templates alongside kit/*.md and SKILL.md files to ensure content follows platform-prefix naming conventions.

Why does the lint check exit with a non-zero code?

The lint check exits non-zero when HIGH severity findings exist in universal kit files. This deterministic behavior ensures CI pipelines fail when platform-prefix drift is detected, preventing broken cross-platform content.

What's the best way to fix platform drift findings in kit files?

To fix platform drift findings, relocate flagged content from universal kit files to appropriate platform-prefixed files like ios-* or web-*. The severity-coded report guides maintainers to the specific files needing content relocation.