discover-project-commands

Inventory project commands from Makefiles and npm scripts into a reference document.

10|2|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/eveld/claude --skill discover-project-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover-project-commands
Source: https://github.com/eveld/claude/tree/main/skills/discover-project-commands
Command: npx skills add https://github.com/eveld/claude --skill discover-project-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly discover and document every runnable command in a codebase, reducing planning time and preventing missed steps when planning work.

Core Features & Use Cases

  • Discovers Makefile targets and documents their purpose from comments
  • Extracts npm scripts from package.json and records their intent
  • Generates a centralized commands reference for planning and execution

Quick Start

Run the discover-project-commands skill during planning to generate thoughts/notes/commands.md with all project commands documented.

Frequently Asked Questions about discover-project-commands

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

FAQPage Schema
How do I automatically document all npm scripts and Makefile targets in a project?

Automatically documenting project commands involves parsing Makefile targets and package.json scripts, extracting their purpose and intent to generate a centralized reference document at thoughts/notes/commands.md.

What is the best way to inventory build commands across diverse languages for planning?

Inventorying build commands across diverse languages involves detecting language-specific build tasks and consolidating them into a reference document to reduce planning time and prevent missed execution steps.

Can I extract the purpose of Makefile targets from comments automatically?

Yes, you can extract the purpose of Makefile targets by parsing the Makefile configurations, capturing the intent behind each target and recording it in a generated commands reference document.

Does project command discovery work with language-specific build tools outside of npm and Makefiles?

Project command discovery works with npm scripts, Makefile targets, and other build tool configurations across diverse languages by detecting language-specific build tasks during the inventory process.

Why generate a centralized commands reference before starting project planning?

Generating a centralized commands reference before planning prevents missed steps during execution by ensuring every runnable command in a codebase is quickly discovered and documented in a single file.