detect-stack

Analyze project manifests and workflows to generate a .agents/stack-context.md.

6|2|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/JordanCoin/codingskills --skill detect-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-stack
Source: https://github.com/JordanCoin/codingskills/tree/main/skills/detect-stack
Command: npx skills add https://github.com/JordanCoin/codingskills --skill detect-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a concise, accurate picture of a codebase’s stack by identifying the primary language, framework, conventions, and CI gates to inform downstream coding principle skills and stack-aware automation.

Core Features & Use Cases

  • Detects the primary programming language and framework from file extensions and common manifests.
  • Infers conventions and CI apparatus by scanning configuration files (workflows, manifests, and scripts).
  • Produces a compact .agents/stack-context.md to standardize stack reference across skills and tooling.
  • Useful when onboarding a new project or aligning multiple skills to a shared context across languages.

Quick Start

Run this skill against a project root to generate the .agents/stack-context.md for that codebase.

Frequently Asked Questions about detect-stack

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

FAQPage Schema
How do I detect the programming language and framework used in a codebase?

Identifying your project stack involves scanning file extensions, package manifests, and workflow configurations. This analysis determines the primary language, framework, build tools, and CI gates present in the codebase.

What is a stack context file and how does it help with project onboarding?

A stack context file is a concise markdown summary of your codebase's language, framework, build tools, and CI gates. It standardizes project references to align downstream coding skills and stack-aware automations to a shared context.

How do I identify CI gates and build conventions from existing configuration files?

CI gates and conventions are identified by scanning workflow configurations, package manifests, and scripts within the project. This infers the continuous integration apparatus and standardizes the results into a compact markdown reference.

Can I generate a project stack summary without manually inspecting every package manifest?

Yes, you can automatically generate a project stack summary by running analysis against the project root. It inspects package manifests and file extensions to produce a concise stack-context markdown file without manual inspection.

Does stack detection work for cross-cutting automation across different programming languages?

Stack detection works across different programming languages by identifying the primary stack from file extensions and manifests. This generates a shared context file that informs downstream coding principles and stack-aware automation across varied environments.