Map repository architecture, data flows, and directory structure into a reconnaissance report.
npx skills add https://github.com/Mord0reK/panel --skill panel-analysis
Please help me install this Agent Skill. Skill: panel-analysis Source: https://github.com/Mord0reK/panel/tree/main/.claude/skills/panel-analysis Command: npx skills add https://github.com/Mord0reK/panel --skill panel-analysis
This skill provides a structured approach to deeply analyze a repository's architecture, data flows, and directory layout before implementing changes, ensuring the team has a clear understanding of how components interact and what needs to be reported to the Orchestrator.
Uruchom ten skill na początku nowego projektu, aby przeprowadzić dogłębny rekonesans architektury i wygenerować zwięziony raport dla Orchestratora.
High-intent search queries and answers about installing and using this skill.
Analyzing repository architecture before implementation involves mapping main components like Agent, Backend, and Frontend, along with their data flows and directory structure. This automated reconnaissance ensures a clear understanding of how modules interact before any coding begins.
Mapping WebSocket and SSE data flows in a codebase requires documenting the data streams, channels, and interaction points between modules. This architectural reconnaissance identifies how components communicate and exchange data across boundaries.
You need to perform codebase architecture reconnaissance at the start of any new project or module. It is essential for mapping cross-component dependencies, understanding interaction points, and preparing a standardized handoff report before development starts.
Yes, you can automate generating an architecture report for a new repository. The process produces a ready-to-submit reconnaissance report that explains architecture, dependencies, and directory structure, directly informing architectural decisions and Orchestrator handoffs.
Yes, repository reconnaissance works for projects with multiple components like Agent, Backend, and Frontend. It maps their specific roles, languages, and boundaries, while documenting the cross-component interface dependencies and interaction points between them.
nguyenpv1980-wqDesign software architecture from inspected codebase components and dependencies.
jctannerAggregate component architecture summaries into a platform-level Markdown document.
paulmalmquistConvert research reports into phased implementation tasks with risk levels and handoff routing.
OniroHuaverGenerates TECH.md specifications for software features from codebase analysis and implementation planning.
