talayash

talayash/agentrium

Skill Claude CodeCodex

Full build/type/lint/security verification pipeline for ClaudeTerminal.

talayash/agentrium

Instructions file

Instructions for talayash/agentrium, covering claude.md, project overview, tech stack, project structure and architecture.

talayash/spring-fleet

Plugin Claude Code

Tools for navigating, tracing, and debugging multi-repo Spring Boot microservice fleets.

talayash/spring-fleet

Plugin Claude Code

OpenTelemetry-native, MCP-first debugging layer for multi-repo Spring Boot microservice fleets. Cross-repo call-chain tracing, traceid-correlated log timelines with code-grounded root-cause hypothesis, and a stdlib MCP server exposing fleet operations as typed tools.

talayash/spring-fleet

MCP server Claude CodeCodexCursor +2

MCP server "spring-fleet" as configured in talayash/spring-fleet. Runs ${CLAUDE_PLUGIN_ROOT}/scripts/mcp_server.py with python. Needs 1 environment variable to run.

talayash/spring-fleet

Agent

Topology-aware code explorer for a fleet of multi-repo Spring Boot microservices. Traces a request or feature across service repos and shared libraries, following inter-service (proxy-lib) calls. Use when you need to understand how a flow works across more than one repo.

talayash/spring-fleet

Agent

Computes the cross-fleet blast radius of a change to a shared-lib symbol, file, or service endpoint - returns every consumer across every service repo with file:line citations, grouped by service and consumer kind.

talayash/spring-fleet

Agent

Reads logs across many Spring Boot services, correlates them by a trace key (e.g. sessionId), reconstructs one cross-service timeline, and isolates the failing hop. Use when debugging a runtime issue that spans services.

talayash/spring-fleet

Command

Debug a runtime failure across the fleet by correlating logs on an OTel traceid / sessionId / requestId — or by reading a pasted Grafana / stack-trace screenshot — and mapping the failure back to source.

talayash/spring-fleet

Command

Scan a repos directory and generate (or update) spring-fleet.config.json for the fleet.

talayash/spring-fleet

Command

Find every consumer of a shared-lib symbol, file, or API across the fleet's service repos — outputs an impact list with file:line citations.

talayash/spring-fleet

Command

Tail or aggregate logs from the fleet's services — file-based when present, kubectl-based when the config has a k8s block (for mirrord / in-cluster runs).

talayash/spring-fleet

Command

Plan or launch the fleet locally — compose-first per service, with stdout tee'd to logDir so /debug can read it later.

talayash/spring-fleet

Command

Trace how an endpoint or feature flows across the fleet's service repos and shared libraries, with file:line citations.

talayash/spring-fleet

Skill Claude CodeCodex

Use when debugging a runtime failure in a locally-running fleet of Spring Boot microservices - correlates logs across services by a trace key, reconstructs the cross-service timeline, isolates the failing hop, and maps it back to source.

talayash/spring-fleet

Skill Claude CodeCodex

Use when a fleet service ships its own Spring AI MCP server - explains how to discover those servers from the spring-fleet config and federate them alongside the spring-fleet MCP tools so the agent has one unified tool surface across the fleet.

talayash/spring-fleet

Skill Claude CodeCodex

Use when fleet logs are console-only or scattered and cross-service correlation needs a stable location - installs a logback convention so every service writes / .log with OTel traceid / spanid and legacy sessionId / requestId in the pattern.

talayash/spring-fleet

Skill Claude CodeCodex

Use when you need to understand how a request, endpoint, or feature flows across multiple Spring Boot service repos and shared libraries - produces an ordered call chain with file:line citations, following inter-service proxy-lib calls.