mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
Add database-admin subagent and update README
- Added database-admin to Infrastructure & Operations section - Updated count from 35 to 36 subagents - Added to usage examples and workflow patterns - Added to Operations & Maintenance guidance section - Specializes in backups, replication, user management, and disaster recovery
This commit is contained in:
@@ -4,7 +4,7 @@ A comprehensive collection of specialized AI subagents for [Claude Code](https:/
|
||||
|
||||
## Overview
|
||||
|
||||
This repository contains 35 specialized subagents that extend Claude Code's capabilities. Each subagent is an expert in a specific domain, automatically invoked based on context or explicitly called when needed.
|
||||
This repository contains 36 specialized subagents that extend Claude Code's capabilities. Each subagent is an expert in a specific domain, automatically invoked based on context or explicitly called when needed.
|
||||
|
||||
## Available Subagents
|
||||
|
||||
@@ -28,6 +28,7 @@ This repository contains 35 specialized subagents that extend Claude Code's capa
|
||||
- **[deployment-engineer](deployment-engineer.md)** - Configure CI/CD pipelines, Docker containers, and cloud deployments
|
||||
- **[cloud-architect](cloud-architect.md)** - Design AWS/Azure/GCP infrastructure and optimize cloud costs
|
||||
- **[database-optimizer](database-optimizer.md)** - Optimize SQL queries, design efficient indexes, and handle database migrations
|
||||
- **[database-admin](database-admin.md)** - Manage database operations, backups, replication, and monitoring
|
||||
- **[terraform-specialist](terraform-specialist.md)** - Write advanced Terraform modules, manage state files, and implement IaC best practices
|
||||
- **[incident-responder](incident-responder.md)** - Handles production incidents with urgency and precision
|
||||
- **[network-engineer](network-engineer.md)** - Debug network connectivity, configure load balancers, and analyze traffic patterns
|
||||
@@ -93,6 +94,7 @@ Mention the subagent by name in your request:
|
||||
"Have devops-troubleshooter analyze these production logs"
|
||||
"Use cloud-architect to design a scalable AWS architecture"
|
||||
"Get network-engineer to debug SSL certificate issues"
|
||||
"Use database-admin to set up backup and replication"
|
||||
|
||||
# Data and AI
|
||||
"Get data-scientist to analyze this customer behavior dataset"
|
||||
@@ -116,6 +118,10 @@ Mention the subagent by name in your request:
|
||||
# Network connectivity workflow
|
||||
"Fix intermittent API timeouts"
|
||||
# Automatically uses: network-engineer → devops-troubleshooter → performance-engineer
|
||||
|
||||
# Database maintenance workflow
|
||||
"Set up disaster recovery for production database"
|
||||
# Automatically uses: database-admin → database-optimizer → incident-responder
|
||||
```
|
||||
|
||||
## Subagent Format
|
||||
@@ -187,6 +193,7 @@ payment-integration → security-auditor → Validated implementation
|
||||
- **devops-troubleshooter**: Production issues, deployment problems
|
||||
- **incident-responder**: Critical outages requiring immediate response
|
||||
- **database-optimizer**: Query performance, indexing strategies
|
||||
- **database-admin**: Backup strategies, replication, user management, disaster recovery
|
||||
- **terraform-specialist**: Infrastructure as Code, Terraform modules, state management
|
||||
- **network-engineer**: Network connectivity, load balancers, SSL/TLS, DNS debugging
|
||||
|
||||
|
||||
31
database-admin.md
Normal file
31
database-admin.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: database-admin
|
||||
description: Manage database operations, backups, replication, and monitoring. Handles user permissions, maintenance tasks, and disaster recovery. Use PROACTIVELY for database setup, operational issues, or recovery procedures.
|
||||
---
|
||||
|
||||
You are a database administrator specializing in operational excellence and reliability.
|
||||
|
||||
## Focus Areas
|
||||
- Backup strategies and disaster recovery
|
||||
- Replication setup (master-slave, multi-master)
|
||||
- User management and access control
|
||||
- Performance monitoring and alerting
|
||||
- Database maintenance (vacuum, analyze, optimize)
|
||||
- High availability and failover procedures
|
||||
|
||||
## Approach
|
||||
1. Automate routine maintenance tasks
|
||||
2. Test backups regularly - untested backups don't exist
|
||||
3. Monitor key metrics (connections, locks, replication lag)
|
||||
4. Document procedures for 3am emergencies
|
||||
5. Plan capacity before hitting limits
|
||||
|
||||
## Output
|
||||
- Backup scripts with retention policies
|
||||
- Replication configuration and monitoring
|
||||
- User permission matrix with least privilege
|
||||
- Monitoring queries and alert thresholds
|
||||
- Maintenance schedule and automation
|
||||
- Disaster recovery runbook with RTO/RPO
|
||||
|
||||
Include connection pooling setup. Show both automated and manual recovery steps.
|
||||
Reference in New Issue
Block a user