Infrastructure troubleshooting plugin for diagnosing and resolving issues across GitHub Actions, Railway, Supabase, and Postgres. Focuses on log analysis, error pattern recognition, and proactive health monitoring.
Full diagnostic workflow for infrastructure issues. Use when something is broken and you need comprehensive troubleshooting.
Find and analyze errors across infrastructure platforms. Use to identify, categorize, and understand recent errors.
Health check across all infrastructure platforms. Use to verify system health, check for advisories, and get an overall status report.
Quick log retrieval from infrastructure platforms. Use to fetch and display logs from GitHub Actions, Railway, Supabase, or Postgres.
Trace issues across the infrastructure stack. Use to follow a request, error, or transaction through multiple systems.
Root cause analysis specialist for infrastructure issues. Use when diagnosing complex errors, determining root causes, and recommending remediation strategies.
Proactive health assessment specialist for infrastructure monitoring. Use when checking overall system health, running health audits, or monitoring for potential issues.
Log parsing and analysis specialist for infrastructure troubleshooting. Use when retrieving, parsing, and analyzing logs from GitHub Actions, Railway, Supabase, or Postgres.
Platform-specific expertise for GitHub Actions, Railway, Supabase, and Postgres. Use when you need deep knowledge about a specific platform's configuration, troubleshooting, or best practices.
Error recognition and diagnosis patterns for infrastructure troubleshooting. Use when identifying, categorizing, or resolving errors across platforms.
Health monitoring knowledge and procedures for infrastructure platforms. Use when assessing system health, running health audits, or setting up monitoring.
Log parsing techniques and analysis methodologies for infrastructure troubleshooting. Use when retrieving, parsing, or analyzing logs from any platform.
Deep knowledge of GitHub Actions, Railway, Supabase, and Postgres platforms. Use when troubleshooting, configuring, or optimizing any of these platforms.
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
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.
A collection of plugins for Claude Code that extend its capabilities with specialized workflows, skills, and agents.
| Plugin | Description | Version |
|---|---|---|
| dotnet-tdd | Test-Driven Development for .NET with SOLID, DRY, KISS, YAGNI, and CQS principles | 1.0.0 |
Install a plugin by pointing Claude Code to the plugin directory:
claude --plugin-dir ./plugins/dotnet-tdd
plugins/
├── dotnet-tdd/ # .NET TDD plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── agents/ # Specialized agents
│ ├── commands/ # Slash commands
│ ├── hooks/ # Event hooks
│ ├── skills/ # Domain knowledge
│ └── README.md
└── [future-plugins]/
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Required: Plugin manifest
├── agents/ # Optional: Subagent definitions
├── commands/ # Optional: Slash commands
├── hooks/ # Optional: Event hooks
├── skills/ # Optional: Knowledge files
└── README.md # Plugin documentation
{
"name": "plugin-name",
"version": "1.0.0",
"description": "What the plugin does",
"keywords": ["relevant", "tags"],
"commands": ["./commands/command.md"],
"agents": ["./agents/agent.md"],
"skills": ["./skills/skill-name"],
"hooks": "./hooks/hooks.json"
}
Want to add a plugin? Submit a PR with your plugin in the plugins/ directory following the structure above.
MIT
npx claudepluginhub doubleslashse/claude-marketplace --plugin infraSenior Business Analyst plugin for requirements gathering, codebase analysis, stakeholder interviews, and SRS document generation
Test-Driven Development plugin for .NET following TDD, SOLID, DRY, KISS, YAGNI, and CQS principles
Lightweight meta-orchestrator that leverages your plugin ecosystem through capability-based routing, with simplified commands (5), consolidated state files (2), and smart continuation
General .NET development workflow with automated validation through build, test, and static analysis quality gates
Workshop facilitation plugin for design thinking, brainstorming, and collaborative problem-solving sessions with guided phases and session artifact documentation
Infrastructure as Code (Terraform, Ansible, CloudFormation), CI/CD pipelines (GitHub Actions, GitLab CI), and database specialists (PostgreSQL, MySQL) for DevOps workflows.
Agents for cloud infrastructure, DevOps, and database operations
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters. Examples:\n\n<example>\nContext: App experiencing slow performance
Infrastructure management for AWS, Kubernetes, Docker, Helm, Fly.io
Plugin-first Claude Code workflows with planning, CI/CD debugging, reusable agents, TODOs, and MCP safety policies.
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n<example>\nContext: Setting up automated deployments\nuser: "We need automatic deployments when we push to main"\nassistant: "I'll set up a complete CI/CD pipeline. Let me use the devops-automator agent to configure automated testing, building, and deployment."\n<commentary>\nAutomated deployments require careful pipeline configuration and proper testing stages.\n</commentary>\n</example>\n\n<example>\nContext: Infrastructure scaling issues\nuser: "Our app crashes when we get traffic spikes"\nassistant: "I'll implement auto-scaling and load balancing. Let me use the devops-automator agent to ensure your infrastructure handles traffic gracefully."\n<commentary>\nScaling requires proper infrastructure setup with monitoring and automatic responses.\n</commentary>\n</example>\n\n<example>\nContext: Monitoring and alerting setup\nuser: "We have no idea when things break in production"\nassistant: "Observability is crucial for rapid iteration. I'll use the devops-automator agent to set up comprehensive monitoring and alerting."\n<commentary>\nProper monitoring enables fast issue detection and resolution in production.\n</commentary>\n</example>