stack-detector

Detect a project's tech stack and write a persistent stack-context cache file.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Hashzin-0/Curion --skill stack-detector-hashzin-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-detector
Source: https://github.com/Hashzin-0/Curion/tree/main/.opencode/skills/skill-stack
Command: npx skills add https://github.com/Hashzin-0/Curion --skill stack-detector-hashzin-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running full stack detection before every task is wasteful and slows automation; this Skill produces a single, authoritative STACK CONTEXT that other skills and agents read instead of re-detecting, ensuring consistent environment assumptions and faster workflows.

Core Features & Use Cases

  • Persistent Cache: Generates and saves a .opencode/stack-context.md file with frontmatter including generated_at and package_json_mtime to enable staleness checks.
  • Comprehensive Detection: Reads package.json, tsconfig.json, env examples, Next/Vite/Tailwind configs, inspects folder layout (app/pages/src), categorizes dependencies, detects monorepos, and records uncertainties with confidence levels.
  • Operational Integration: Intended for onboarding to unfamiliar repos, before large or gigantic tasks, and as an orchestrator-invoked prerequisite to avoid redundant scans.

Quick Start

Run the stack-detector to analyze the repository and write a fresh .opencode/stack-context.md cache.

Frequently Asked Questions about stack-detector

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

FAQPage Schema
How do I detect a project's tech stack and cache it for automated workflows?

Stack detection involves reading root configuration files like package.json and tsconfig.json, categorizing dependencies, and writing a persistent cache file to establish a single source of truth about the project's framework, routing, and tooling.

What is the best way to analyze a Next.js project structure for large refactors?

Analyzing a Next.js project structure for refactors is best handled by scanning folder layouts like app or pages directories, reading configuration files, and generating a cached stack context to avoid redundant scans during large automated tasks.

How do I check if my project's cached tech stack context is stale?

You can check if your cached tech stack context is stale by comparing the generated_at timestamp and package_json_mtime frontmatter in the .opencode/stack-context.md file against the current package.json modification time.

Does stack detection work with monorepos and multiple dependency configurations?

Stack detection works with monorepos by inspecting the folder layout, reading root configuration files, and categorizing dependencies across the project, while recording any uncertainties with confidence levels in the final cache file.

Why should I generate a stack context before running automated codebase tasks?

Generating a stack context before automated codebase tasks prevents wasteful repeated environment scans, providing other agents and skills with an authoritative source of truth about framework and tooling for faster, consistent operations.