software-system-analyzer

Solid

Detects repository context, maps dependencies (enterprise-specific or general), and generates/persists architectural documentation.

Data & Documents 1 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## What I do I analyze the current repository to determine its origin and architecture. If it is hosted on a private enterprise Sourcegraph instance, I execute a deep internal discovery protocol using the /sourcegraph-search skill. Otherwise, I perform a comprehensive local audit of language, frameworks, and public dependencies. ## When to use me Trigger this skill immediately upon entering a new repository or when the user asks "How does this system work?", "What is the architecture", "What are the system dependencies?", or "What should I know to work on this codebase?". ## Operational Workflow ### Phase 1: Context Detection Run `gh repo view --json url` or inspect the local `.git/config` to check the remote host. - **IF host is a private enterprise Sourcegraph instance:** Proceed to Phase 2 (Enterprise Protocol). - **OTHERWISE:** Proceed to Phase 3 (General Protocol). ### Phase 2: Enterprise Sourcegraph Discovery Protocol Use `src search` to map the ecosystem. Adapt the repo patterns to your organization's Sourcegraph instance: 1. **Contracts:** Search for the organization's interface definition contracts repository for Thrift IDL, Proto schema, GraphQL, etc... 2. **Message Queues:** Search for message broker (e.g., Kafka) infrastructure-as-code repositories. 3. **Cloud/IAM:** Search for cloud infrastructure bootstrap or service provisioning repositories. 4. **Data Pipelines:** Search for ETL job or data pipeline deployer repositories. 5. **Data Stores:** Search for dat...

Details

Author
tkolleh
Repository
tkolleh/skills
Created
3 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

explain-my-code

This skill should be used when the user asks to "document this codebase", "explain my code", "generate architecture docs", "write an onboarding doc", "analyze this repo", or wants self-contained technical documentation produced from source. Signal tokens include "codebase", "repo", "architecture diagram", "onboarding", "system overview", "tech stack", ".md doc". Casual phrasings (when paired with an onboarding/documentation intent) include "help a new dev understand this whole codebase", "write up how this project works", "map out this code into a doc". Also trigger when the user points at a repository and asks for a single Markdown write-up with Mermaid diagrams. Do NOT use for a quick one-line "what does this do" answer, for line-by-line code review or bug-finding (that is wordpress-architect-review or a review skill), for refactoring or modernization plans (that is refactoring-analyst), or for producing diagrams alone (that is codebase-to-mermaid).

2 Updated 3 days ago
chrismccoy
AI & Automation Solid

project-researcher

Scans, analyzes, and documents the existing repository architecture, directories, and file purposes into docs/ARCHITECTURE.md.

43 Updated today
GulajavaMinistudio
Data & Documents Solid

architectural-analysis

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for writing documentation or architectural decision records.

128 Updated today
testdouble