Correlates and troubleshoots logs across OS, AWS, application, and web server sources. Extensible via log-types/ definitions.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub realdougeubanks/claudemarketplace --plugin log-correlationStructured engineering code review covering readability, complexity, test gaps, SOLID principles, and API consistency.
Designs and reviews REST, GraphQL, and gRPC APIs. Produces OpenAPI specs, GraphQL schemas, and proto files.
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.
Full async multi-agent development workflow: Planning → Design → Dev → Security/Tech Review loop with file-based handoffs and release-branch Git model.
Generates a comprehensive developer onboarding guide (ONBOARDING.md) by reading the codebase: directory map, entry points, environment variables, key commands, and architecture overview.
Log API requests with structured logging and correlation IDs
Auto-capture development command output and search/analyze with Claude Code
Structured logging with proper levels, context, PII handling, centralized aggregation. Use for application logging, log management integration, distributed tracing, or encountering log bloat, PII exposure, missing context errors.
Backend platform discipline: observability, API design, and service architecture practices
Core skills: ecosystem guide, skill creator, research patterns, session reflection, and plugin development. Includes UserPromptSubmit hook for forced skill evaluation.
Analyze Claude Code agent session transcripts to identify inefficiencies, anti-patterns, repeated mistakes, missing tooling opportunities, and user frustration signals for continuous improvement