Generate JSON metadata files tracking codebase architecture and dependencies.
npx skills add https://github.com/nnexai/git-stacks --skill gsd-intel-nnexai
Please help me install this Agent Skill. Skill: gsd-intel Source: https://github.com/nnexai/git-stacks/tree/main/.github/skills/gsd-intel Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-intel-nnexai
This Skill solves the problem of codebase fragmentation by maintaining a searchable, structured index of architectural decisions, API maps, and dependency graphs that stay synchronized with the source code.
Use the gsd-intel skill to refresh the codebase intelligence index and then query for the term authentication.
High-intent search queries and answers about installing and using this skill.
To maintain codebase architecture and dependencies, you can use automated source code analysis to generate JSON-based metadata files. This creates a searchable intelligence index that tracks structural relationships and stays synchronized with your source code.
Yes, you can query for specific API patterns across your codebase using inline terminal searches. The intelligence index allows developers to search for architectural patterns and specific terms rapidly without leaving their current development environment.
The best way to track structural changes in a codebase is by performing status checks and diffs against an intelligence snapshot. This identifies exactly what has changed in the architecture and dependencies since the last analysis was generated.
Yes, you need gsd-tools to generate codebase intelligence metadata. The integration with gsd-tools is required to perform the source code extraction, validation, and status reporting tasks necessary for building the architectural index.
Automated codebase analysis generates API maps and project health metadata by extracting architectural decisions and dependency graphs from source code. It outputs structured JSON-based intel files that document stack architecture and API exports for rapid retrieval.
Codebase fragmentation makes architecture retrieval difficult because structural decisions and dependency relationships become scattered across source files. A synchronized intelligence index solves this by maintaining a structured, searchable map of API exports and architecture.
thktGenerate architecture overview Markdown and Mermaid diagrams from codebase analysis.
silaslopes100Map legacy software project structure, languages, and configuration files.
tinner-deinnoRoute user intent to the correct codebase intelligence workflow.
phuhao00Analyze source code to identify symbols, call graphs, and architectural patterns.
