workspace-lint

Audit workspace structural contracts and report drift as pass/fail.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jennyfirrr/workspace-template --skill workspace-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-lint
Source: https://github.com/Jennyfirrr/workspace-template/tree/main/claude-skills/workspace-lint
Command: npx skills add https://github.com/Jennyfirrr/workspace-template --skill workspace-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workspace-lint frontloads a contract that the workspace must obey; it self-audits the workspace against structural rules, validates frontmatter, ensures the plan-before-code gate is wired, and enforces the public/private boundary and manifest consistency.

Core Features & Use Cases

  • Self-audit: verifies every skill's SKILL.md frontmatter is valid and its customization aggregates cleanly; ensures the plan gate and boundary tools are wired; checks indexes and manifest alignment; reports drift as a pass/fail list without auto-fixing.
  • CI integration: runs in pre-commit and CI to catch structural drift early; supports routing findings to repair skills (/index-rebuild, /resync, or /new-check) to maintain integrity.
  • Design discipline: enforces the workspace's contract across host/workspace boundaries, private tool placement, and symlink resolution.

Quick Start

Run /workspace-lint to perform a full drift audit of the workspace.

Frequently Asked Questions about workspace-lint

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

FAQPage Schema
How do I audit my workspace for structural drift and configuration inconsistencies?

Workspace auditing for structural drift involves validating SKILL.md frontmatter and checking plan gate wiring, public/private boundaries, and manifest alignment. Running a self-audit reports configuration drift as a pass/fail list without auto-fixing.

What is workspace drift and how does a structural contract audit detect it?

Workspace drift occurs when files diverge from established structural contracts. A self-audit detects this by verifying frontmatter validity, enforcing the plan-before-code gate, checking index freshness, and validating manifest alignment against defined host boundaries.

Can I integrate workspace validation and drift detection into my CI pipeline?

Yes, workspace validation supports CI integration and pre-commit hooks to catch structural drift early. It enforces host-reading tool safety and boundary rules, routing findings to repair skills like index-rebuild or resync to maintain integrity.

Does the workspace audit automatically fix boundary violations and manifest misalignment?

No, the workspace audit does not auto-fix issues. It reports structural drift, boundary violations, and manifest misalignment as a pass/fail list, routing findings to dedicated repair skills like resync, index-rebuild, or new-check for resolution.

When should I run a workspace structural audit to catch configuration drift?

Run a workspace structural audit whenever skills, settings.json, or host boundaries change. This verifies consistency, enforces the plan-before-code gate wiring, validates public/private tool placement, and ensures symlink resolution before drift propagates.