skills.rest
flavien-ia
flavien-iaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

_detect-project-root

Detect Next.js project structure and return environment variables for automation workflows.

34|6|Updated Jun 30, 2026
Search Tags:#automation#configuration#monorepo#environment#detection#nextjs
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill detect-project-root
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: _detect-project-root
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_detect-project-root
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill detect-project-root

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates manual environment configuration errors by automatically identifying the project's architecture, ensuring that subsequent automation tasks have the correct context regarding monorepo status, web directory paths, and framework dependencies.

Core Features & Use Cases

  • Automated Detection: Identifies project name, monorepo vs. single-app structure, and Next.js framework usage.
  • Standardized Context: Provides a consistent set of variables (PROJECT_NAME, WEB_DIR, IS_MONOREPO, IS_NEXTJS) to other automation skills.
  • Use Case: When running a new deployment or database migration, this skill ensures the system knows exactly where the web application resides, preventing path-related failures.

Quick Start

Invoke the detect project root skill to initialize the environment variables for the current project.

Frequently Asked Questions about _detect-project-root

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

FAQPage Schema
How do I automatically detect a Next.js project root in a monorepo?▼

To detect a Next.js project root in a monorepo, analyze file system markers like package.json and directory layouts. This identifies the web directory path and monorepo status, returning standardized variables for automation workflows.

What is the best way to prevent path-related failures during automated deployments?▼

Preventing path-related failures during deployment requires automated detection of your project architecture. By identifying monorepo status and web directory paths, you ensure automation tasks have the correct environment context.

How do I get standardized environment variables for my Next.js automation workflows?▼

Get standardized environment variables for Next.js automation workflows by analyzing project structure to output consistent metadata. This provides variables like PROJECT_NAME, WEB_DIR, IS_MONOREPO, and IS_NEXTJS to downstream tasks.

Does automated project structure detection work with both single-app and monorepo layouts?▼

Automated project structure detection works with both single-app and monorepo layouts. It analyzes directory structures and package.json markers to determine monorepo status and framework compatibility for your deployment workflows.

Why do my database migration scripts fail to locate the correct web application directory?▼

Database migration scripts fail to locate the web application directory due to manual environment configuration errors. Automated detection of your project structure resolves this by providing the correct path context for downstream tasks.

Related Skills

Explore More Software Engineering Skills→
goffitygoffity

cleanup

Delete old auto-captured files and draft learnings by retention policy.

Community
Intermediate
Open330Open330
1

preparing-iac-deployment

Analyze projects to generate Dockerfiles, Kubernetes manifests, and CI/CD workflows.

Official
Advanced
thejustinwalshthejustinwalsh
28

turborepo

Configure turbo.json pipelines and caching for Turborepo monorepos.

Community
Advanced
zapabobzapabob
2

shell

Execute literal shell commands in the terminal environment.

Community
Basic