clark-survey

Detect vocabulary drift, naming violations, architectural drift, and test health across codebases.

4|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/outfitter-dev/trails --skill clark-survey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clark-survey
Source: https://github.com/outfitter-dev/trails/tree/main/.claude/skills/clark-survey
Command: npx skills add https://github.com/outfitter-dev/trails --skill clark-survey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect vocabulary drift, naming convention violations, architectural drift, documentation staleness, and test health across a codebase.

Core Features & Use Cases

  • Regularly scan large repositories for vocabulary drift, naming inconsistencies, and emerging architectural patterns.
  • Surface documentation gaps and test health issues with prioritized findings suitable for remediation planning.
  • Use during scheduled health checks or on-demand audits to maintain codebase hygiene and governance alignment.

Quick Start

Run Clark: Survey on your repository to generate a prioritized health findings report.

Frequently Asked Questions about clark-survey

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

FAQPage Schema
How do I detect vocabulary drift and naming convention violations in a codebase?

Detect vocabulary drift and naming convention violations by running autonomous codebase health scans that analyze your repository for inconsistencies. The scan produces deterministic findings that reference governance documents to guide remediation.

What is architectural drift and how does a codebase scan identify it?

Architectural drift occurs when codebase structure diverges from established design patterns over time. A health scan identifies this by analyzing the repository against governance documents to surface prioritized, deterministic findings for remediation.

Can I schedule nightly or weekly codebase health checks across multiple projects?

Yes, you can schedule nightly or weekly codebase health checks across multiple projects. The scan is specifically designed for regular scheduling and on-demand audits to maintain hygiene and governance alignment.

How do I surface documentation gaps and test health issues for remediation planning?

Surface documentation gaps and test health issues by running an autonomous codebase scan. It generates a prioritized findings report highlighting staleness and test failures to help teams plan remediation effectively.

Does the codebase health scan produce output suitable for Linear issue creation?

Yes, the codebase health scan produces deterministic findings suitable for Linear issue creation. It surfaces prioritized results for vocabulary drift, naming violations, and architectural issues to streamline tracking.