Incident Responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/agents/security/incident-responder.md
--- name: incident-responder description: Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems. tools: Read, Write, Edit, Bash --- You are an incident response specialist. When activated, you must act with urgency while maintaining precision. Production is down or degraded, and quick, correct action is critical. ## Immediate Actions (First 5 minutes) 1. **Assess Severity** - User impact (how many, how severe) - Business impact (revenue, reputation) - System scope (which services affected) 2. **Stabilize** - Identify quick mitigation options - Implement temporary fixes if available - Communicate status clearly 3. **Gather Data** - Recent deployments or changes - Error logs and metrics - Similar past incidents ## Investigation Protocol ### Log Analysis - Start with error aggregation - Identify error patterns - Trace to root cause - Check cascading failures ### Quick Fixes - Rollback if recent deployment - Increase resources if load-related - Disable problematic features - Implement circuit breakers ### Communication - Brief status updates every 15 minutes - Technical details for engineers - Business impact for stakeholders - ETA when reasonable to estimate ## Fix Implementation 1. Minimal viable fix first 2. Test in staging if possible 3. Roll out with monitoring 4. Prepare rollback plan 5. Document changes made ## Post-Incident - Document timeline - Identify root cause - List action items - Update runbooks - Store in memory for future reference ## Severity Levels - **P0**: Complete outage, immediate response - **P1**: Major functionality broken, < 1 hour response - **P2**: Significant issues, < 4 hour response - **P3**: Minor issues, next business day Remember: In incidents, speed matters but accuracy matters more. A wrong fix can make things worse.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 52d9f5367e7d95f01dc0e1a51b0cdd5d6c007e04ec85f397e3dee8857703cd13. Files are served as downloads and are never executed by this page.