agent-runbook-generator · packages
Every package shipped from reaatech/agent-runbook-generator, published or pending.
15 packages · page 1 of 2
@reaatech/agent-runbook
Provides a shared library of TypeScript interfaces, Zod schemas, and utility functions for defining and validating service runbooks, incident workflows, and alert configurations. It serves as the core type and validation layer for the Agent Runbook ecosystem, requiring only `zod` as a runtime dependency.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-agent
Provides a unified interface for interacting with Anthropic, OpenAI, and Google Gemini models to perform automated repository analysis and runbook generation. It exposes an `AnalysisAgent` class and factory function that handle provider-specific prompt formatting, response parsing, and template management.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-alerts
Extracts existing monitoring configurations and generates new SLO-based, resource, and application alert definitions for Prometheus, Datadog, and CloudWatch. It provides a collection of utility functions for parsing alert rules, calculating threshold recommendations, and formatting output for specific monitoring platforms.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-analyzer
Extracts technical metadata from service repositories, including language, framework, deployment platform, dependencies, and API endpoints. It provides a set of utility functions that return structured objects representing the analyzed codebase configuration.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-cli
Provides a CLI and programmatic interface to analyze service repositories and generate operator runbooks using LLM-based orchestration. It also functions as a central barrel package that re-exports the entire `@reaatech/agent-runbook` ecosystem and includes an MCP server mode for integration with AI coding agents.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-dashboards
Generates Grafana and CloudWatch dashboard configurations by analyzing code patterns to identify relevant service metrics. It provides functions to extract metrics from a repository and format them into platform-specific dashboard JSON or configuration objects.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-e2e
Description pending.
- status
- awaiting publish
@reaatech/agent-runbook-failure-modes
Analyzes local codebases to identify failure points and generates corresponding mitigation strategies like retry policies and circuit breaker configurations. It provides a set of utility functions to perform risk scoring, retrieve failure mode definitions, and suggest infrastructure hardening patterns.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-health-checks
Analyzes codebases to identify existing health check patterns and generates Kubernetes probe YAML, load balancer configurations, and endpoint implementations. It provides a set of utility functions for automating the creation of service health definitions based on provided analysis contexts.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-incident
Generates severity-based incident response workflows, escalation policies, and communication templates for automated runbooks. It provides a set of utility functions for configuring these procedures and applying dynamic variables to pre-built notification and postmortem templates.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-mcp
Exposes runbook analysis, generation, and validation capabilities as an MCP server that provides 16 tools for AI agents. It offers a `RunbookMCPServer` class and a factory function that communicates via stdio, requiring the `@modelcontextprotocol/sdk` at runtime.
- status
- published
- published
- 2 days ago
@reaatech/agent-runbook-observability
Provides a unified observability layer for agent-based runbook generation, offering a set of initialization functions and helpers for Pino logging, OpenTelemetry tracing, and Prometheus-compatible metrics. It requires an OpenTelemetry Collector endpoint to export telemetry data for cost, quality, and performance monitoring.
- status
- published
- published
- 2 days ago