team-shinchan:lint-harness

Detects misconfigurations in Tailwind CSS v4 and v3 projects, including:structure, oprators, and more.

8|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-lint-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-shinchan:lint-harness
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/lint-harness
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-lint-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The lint harness identifies inconsistent plugin metadata, structural mismatches, and configuration drift that cause failed workflows, hallucinated agent behavior, and unexpected runtime errors in a Claude Code harness.

Core Features & Use Cases

  • Agent frontmatter validation: verifies required fields like name, description, maxTurns, and permissionMode for every agent.
  • Structural integrity checks: ensures skill-command parity, hook registration, and cross-reference consistency across the harness.
  • Drift detection and reporting: validates output-format references, self-check references, and version alignment, producing JSON or human-readable table reports for CI or maintenance audits. Use case: run the harness before a release to catch missing frontmatter, broken hooks, or version mismatches across 15 specialized agents.

Quick Start

Run the lint harness for the repository and return a JSON report of all failing checks.

Frequently Asked Questions about team-shinchan:lint-harness

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

FAQPage Schema
How do I detect configuration drift and plugin inconsistencies in a Claude Code harness?

Configuration drift in a Claude Code harness is detected by running structured lint checks that validate agent frontmatter, hook registrations, and cross-reference consistency. The harness produces JSON or colored-table reports to highlight missing metadata and version mismatches across specialized agents.

What causes hallucinated agent behavior and failed workflows in Claude Code plugin repositories?

Hallucinated agent behavior and failed workflows are caused by inconsistent plugin metadata, structural mismatches, and configuration drift. Missing required agent frontmatter fields like name, description, maxTurns, and permissionMode disrupt runtime validation across specialized agents.

How do I validate agent frontmatter and hook registrations before a CI release?

Agent frontmatter and hook registrations are validated by running a lint harness that verifies required fields and cross-reference consistency across plugin repositories. The harness generates colored-table reports and writes a timestamp file for CI maintenance audits.

Do I need external dependencies to run Node.js lint checks for plugin drift detection?

No external dependencies are required to run Node.js lint checks for plugin drift detection. The lint harness executes natively in Node.js to validate structural integrity and output format references without additional package installations.

Can I output lint check results as structured JSON for automated maintenance workflows?

Yes, lint check results can be output as structured JSON for automated maintenance workflows. The harness produces both JSON and colored-table reports to support CI pipelines and manual audits of version alignment and skill-command parity.