ELYRAON Repo Health Check Lite

Audit your codebase for hygiene issues without the risks of runtime execution or external API calls. Many static analysis tools are too heavy or require complex environment setups just to find missing configuration files or potential security leaks. This skill performs a filename-based hygiene check and static config audit using a local Python helper. It identifies missing project standards, exposed credential paths, and malformed repository structures while keeping your data local.

What it does

• Structure auditing validates presence of essential project files like README, LICENSE, and config manifests.
• Credential detection flags common file paths and naming patterns associated with leaked secrets or logs.
• Resource inventorying scans up to 5,000 files to map repository layout and size constraints.
• Static evidence collection extracts specific line evidence and relative paths for manual review.
• JSON reporting generates structured audit data compatible with custom CI/CD scripts or documentation.

How it works

1. Point the agent to a local repository directory or a stable snapshot.
2. The agent executes a bundled Python helper script to scan the filesystem.
3. The tool parses the JSON output to verify scan status and inventory limits.
4. You receive a report detailing specific finding codes, relative paths, and line-level evidence.

Frameworks & tools

This skill uses a bundled Python 3 standard library helper. It operates entirely via local terminal and filesystem commands without requiring Node.js, Docker, or external cloud services.

Why this beats prompting it yourself

Generic prompts often hallucinate file contents or miss hidden dotfiles in large directories. This skill uses a deterministic Python script to ensure every file within the 20MB limit is actually inventoried and checked against a stable schema.

Use cases

• Perform a quick hygiene check on a new open-source clone before exploration.
• Audit a repository for accidentally committed .env or log files.
• Verify that a project meets basic scaffolding requirements before a release.

Known limitations

Does not execute code or run tests. Maximum 5,000 files or 20MB aggregate size. Individual files over 1MB are skipped. Symlinks and non-regular files are ignored.