By wshobson
Write blameless postmortems with structured root cause analysis, timelines, and action items for incident reviews and post-incident improvement.
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.
Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security
Dependency auditing, version management, and security vulnerability scanning
SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening
Database architecture, schema design, and SQL optimization for production systems
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
npx claudepluginhub p/wshobson-wshobson-postmortem-writing-plugins-incident-response-skills-postmortem-writingDevsForge incident report generator with root cause analysis, timeline tracking, and post-mortem documentation
End-to-end incident postmortem generator. Paste an incident issue URL (Azure DevOps or Jira) and the agent gathers evidence from chat (Slack/Teams), the tracker (related issues, history), Datadog logs, and merged pull requests; reconstructs a chronological timeline with evidence tags; and writes a Google-SRE-style blameless postmortem (summary, impact, timeline, root cause, contributing factors, what went well/wrong, action items, lessons learned). Tracker-agnostic via issuekit. Bundles incident-timeline-builder and postmortem-writer skills.
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.
Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record, Debugging Log Analyser, PR Description Writer, System Design Interview, Changelog Generator, Test Strategy Doc, Runbook Writer, CI/CD Playbook, SLO & Error Budget, Developer Onboarding Doc, On-Call Runbook, Security Threat Model, Performance Budget, Database Schema Design, Database Migration Plan, Technical Debt Register, RFC Writer, Capacity Planning, Load Testing Plan, Disaster Recovery Plan, Feature Flag Guide, Dependency Audit, Service Catalog Entry, Monitoring Setup Guide, Local Dev Setup, API Versioning Strategy, Infra-as-Code Review, Engineering Weekly Report, Tech Radar, Sprint Velocity Analysis, Microservices Decomposition, Engineering Hiring Rubric, Context Mode, Claude Superpowers, Skill Security Auditor, Error Decoder, Regex Builder, Git Troubleshooter, Dependency Conflict Resolver, Code Explainer, Writing Great Skills. 44 structured skills for engineering teams, SREs, technical PMs, and Claude Code power users — including a meta-skill for authoring high-quality SKILL.md files.
Structured operational documentation and runbook patterns for human operators. Helps create clear, actionable runbooks for troubleshooting, incident response, and maintenance.
Incident response and breach management including IR planning, forensics, incident communication, containment, and post-incident analysis.