collect-system-status

Collects system status from repositories into a structured markdown report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill collect-system-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect-system-status
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/collect-system-status
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill collect-system-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a repeatable, code-centric snapshot of a repository so technical managers and engineers can quickly understand project structure, counts, and key configuration without manual inspection.

Core Features & Use Cases

  • Automated repository auditing: Parse docker-compose files, enumerate services and profiles, and extract port mappings for operational visibility.
  • Cross‑subsystem counts and inspection: Count backend routers, models, services, and tests; enumerate frontend components, views, stores, and API clients; and tally firmware source files and PlatformIO environments.
  • CI and agent visibility with reporting: List GitHub workflows, Makefile targets, and agent/skill/report artifacts and produce a single markdown report delivered to the Technical Manager inbox for handover or triage.

Quick Start

Run the collect-system-status skill to analyze the repository and save the generated system-status-from-code.md report to the Technical Manager inbox.

Frequently Asked Questions about collect-system-status

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

FAQPage Schema
How do I generate a system status report for a multi-component repository?

To generate a system status report, you need an automated tool that parses docker-compose files, counts backend routers and frontend components, inspects ESP32 firmware, and writes a structured markdown file summarizing the codebase.

What is included in an automated codebase audit for technical handovers?

An automated codebase audit includes file counts, backend service configurations, frontend component enumerations, PlatformIO environments, GitHub workflows, and Makefile targets, delivering a comprehensive markdown report for manager briefings.

Can I audit ESP32 firmware and Vue frontend components in the same repository scan?

Yes, you can audit ESP32 firmware and Vue frontend components simultaneously by running a skill that inspects PlatformIO environments, enumerates frontend views and API clients, and tallies firmware source files in one pass.

How do I parse docker-compose files and extract port mappings for a technical report?

Parsing docker-compose files to extract port mappings requires an automation tool that reads service profiles and configurations, then compiles the extracted operational data into a structured markdown technical report.

Does this system status tool work with repositories containing GitHub workflows and Makefile targets?

Yes, the system status tool works with repositories containing GitHub workflows and Makefile targets by listing CI configurations and build targets alongside backend Python services and agent directories in the final report.