dot-scout

Analyze a project and create or update .principles files with an audit trail.

261|57|Updated Feb 9, 2022
One-click install
npx skills add https://github.com/robocode-dev/tank-royale --skill dot-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dot-scout
Source: https://github.com/robocode-dev/tank-royale/tree/main/.agents/skills/dot-scout
Command: npx skills add https://github.com/robocode-dev/tank-royale --skill dot-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyse a project to determine which principles apply and create or update .principles files encoding that analysis.

Core Features & Use Cases

  • Detect applicable principles across a codebase and map them to .principles files.
  • Create new principle entries or update existing ones to reflect current findings.
  • Generate a reproducible, audit-friendly trail of decisions for code governance.

Quick Start

Run the dot-scout command against your project directory to generate and update .principles files.

Frequently Asked Questions about dot-scout

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

FAQPage Schema
How do I map coding principles to a project directory automatically?

To map principles to a project directory, the tool resolves the target path, locates the git root, and runs a structured workflow to detect applicable principles and generate or update .principles files encoding that analysis.

What is a .principles file used for in code governance?

A .principles file encodes an auditable trail of decisions by mapping applicable coding principles to a specific codebase, generating a reproducible record for code governance and static analysis tracking.

Can I use static analysis to detect which principles apply to any repository?

Yes, you can apply static analysis to any repository by resolving a target directory and locating the git root to detect applicable principles and write updates to .principles files.

How do I update existing principle entries in my codebase?

To update existing principle entries, the analysis workflow reads your current .principles files, evaluates the codebase for new findings, and writes updates to reflect the current state while outputting an auditable decision trail.

Do I need a git repository to generate principle files for my project?

Yes, you need a git repository because the workflow resolves the target directory and locates the git root before running the structured analysis to create or update .principles files.

What's the best way to create an auditable trail of code quality decisions?

The best way to create an auditable trail is to run a structured workflow that maps principles into codebases, generating reproducible .principles files that document every analysis decision for code governance.