sdd-explore-tech

Detects languages, frameworks, and tooling from repository manifests and writes tech.md.

Updated Aug 2, 2026

Search Tags:#documentation #tech stack #manifest #detection #sdd #ci #repository scan

Ready to run

npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-explore-tech-phm-aguiar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-explore-tech
Source: https://github.com/phm-aguiar/test_documentacao/tree/main/.claude/skills/sdd-explore-tech
Command: npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-explore-tech-phm-aguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Manually documenting a project's technology stack is error-prone and quickly becomes outdated. This Skill scans the actual repository files and generates an accurate tech.md document reflecting only what is really in the codebase. ## Core Features & Use Cases - Manifest Detection: Identifies languages and frameworks from go.mod, package.json, Cargo.toml, pom.xml, requirements.txt, and other manifest files. - Tooling Discovery: Detects CI workflows, linters, Docker files, task runners, and test patterns across the repository. - Template-Based Output: Fills a canonical tech.md template in .github/memory/ with detected data, using em-dashes for anything not found. - Use Case: After initializing a spec-driven development workspace, run this Skill to populate .github/memory/tech.md so downstream documentation and planning steps have an accurate view of the stack. ## Quick Start Ask the assistant to scan this repository and fill .github/memory/tech.md with the detected technology stack.

Frequently Asked Questions about sdd-explore-tech

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

FAQPage Schema

How do I automatically detect the tech stack of a repository?▼

Run this Skill after initializing the .github/memory/ directory. It scans manifest files like go.mod, package.json, Cargo.toml, and requirements.txt, then writes the detected languages, frameworks, and tools into .github/memory/tech.md.

Which languages and manifest files are detected?▼

Detection covers Go (go.mod), Node.js/TypeScript (package.json), Rust (Cargo.toml), Java/Kotlin (pom.xml, build.gradle), Python (requirements.txt, pyproject.toml, setup.py), Ruby (Gemfile), Elixir (mix.exs), C/C++ (CMakeLists.txt), and .NET (csproj, sln).

Does it detect CI pipelines and linters too?▼

Yes. It scans .github/workflows/ for CI pipelines, looks for linter configs like .golangci.yml and .eslintrc, finds Dockerfiles and docker-compose files, and identifies task runners such as Makefile and justfile plus common test file patterns.

What happens if tech.md already exists?▼

The Skill asks whether to overwrite or merge before making changes. It never silently replaces an existing tech.md, so previously curated content is protected from accidental loss.

What if no manifest files are found in the repository?▼

The Skill warns that the repository may be empty or use an unsupported language. Fields without detected evidence are filled with an em-dash rather than guessed values, since inventing stack entries is explicitly forbidden.