detect-project-type

Detect project type and generate structured release configurations.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/jayteealao/Aperture --skill detect-project-type
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-project-type
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/detect-project-type
Command: npx skills add https://github.com/jayteealao/Aperture --skill detect-project-type

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Detect Project Type skill analyzes a project directory to determine its type (Node.js, Python, Rust, Go, Java, Claude Code plugin, or monorepo) and loads or generates an appropriate release configuration. This is the foundation for generic release automation that works with any application.

Core Features & Use Cases

  • Auto-detects project type based on common markers (package.json, Cargo.toml, pyproject.toml, etc.)
  • Identifies version sources, changelog locations, and suitable tag patterns
  • Generates a structured release configuration usable by downstream automation tools
  • Use Case: In a multi-repo setup, quickly generate per-repo release configs for CI pipelines without manual config

Quick Start

Run the detect-project-type skill at the root of your project to produce a release-config scaffold and project_type output.

Frequently Asked Questions about detect-project-type

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

FAQPage Schema
How do I auto-detect project type and generate a release config for a monorepo?

To auto-detect project type, run the skill at your project root. It analyzes files like package.json or Cargo.toml to output a structured release configuration including project_type, version_files, changelog_file, and tag_pattern for your monorepo.

What's the best way to identify version sources and changelog locations for CI pipelines?

The best way to identify version sources is using automated project detection. It validates the presence and locations of version files and changelogs, generating a structured configuration usable by downstream CI pipeline automation tools without manual setup.

Does release config auto-detection work with Python, Rust, and Go language ecosystems?

Yes, release config auto-detection works with Python, Rust, and Go. It also supports Node.js, Java, Claude Code plugins, and monorepos by analyzing language-specific markers like pyproject.toml to determine appropriate release configurations.

Can I generate per-repo release configurations in a multi-repo setup without manual config?

Yes, you can generate per-repo release configurations without manual config. By running project type detection in each repository, it scaffolds the necessary release settings including tag patterns and changelog locations for multi-repo setups.

When do I need to explicitly define a tag pattern versus using auto-detected configurations?

You need to explicitly define a tag pattern when your release workflow deviates from standard conventions. Otherwise, the skill auto-detects configurations by analyzing your project structure and applies suitable tag patterns automatically.