How does the skill detect repository commands?

It scans the repository for configuration files like Makefiles, package manifests (package.json), and CI/CD configs to infer standard tasks.

Can I manually update the confidence levels?

The skill manages confidence levels through verification, but because it outputs to standard files, users can review and adjust the findings as needed.

Where does the skill store the detected commands?

All identified commands are saved in COMMANDS.md and COMMANDS.json within the repository for both human and machine readability.

Is it safe to run commands with this skill?

Yes, the skill includes guardrails that prevent the execution of destructive commands and marks unverified scripts with a low confidence score.

Command Auto-Discovery

Name: Command Auto-Discovery
Author: CheekyCodexConjurer

byCheekyCodexConjurer

Deployment & DevOps

Automatically identifies and verifies installation, testing, linting, and build commands within any repository.

About

The Command Auto-Discovery skill streamlines the development workflow by programmatically inferring standard repository commands from manifests such as Makefiles, package.json files, and CI configurations. It intelligently detects scripts for installation, testing, linting, and building, recording them in structured COMMANDS.md and COMMANDS.json files. By assigning confidence levels to discovered commands and providing safe verification steps, it ensures that Claude can interact with your codebase using the correct tools and project-specific scripts without manual intervention.

Key Features

Categorization of test, lint, build, and install commands
Safety guardrails to prevent execution of destructive scripts
Confidence-based verification system for command reliability
Automated manifest scanning for Makefiles and package managers
Structured data output to COMMANDS.json and markdown documentation
0 GitHub stars

Use Cases

Automating the setup process for new development environments
Standardizing project command documentation for automated CI/CD integration
Quickly onboarding to unfamiliar or legacy repositories to find build scripts

About

Key Features

Categorization of test, lint, build, and install commands
Safety guardrails to prevent execution of destructive scripts
Confidence-based verification system for command reliability
Automated manifest scanning for Makefiles and package managers
Structured data output to COMMANDS.json and markdown documentation
0 GitHub stars

Use Cases

Automating the setup process for new development environments
Standardizing project command documentation for automated CI/CD integration
Quickly onboarding to unfamiliar or legacy repositories to find build scripts