arjunprabhul
5 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
arjunprabhulalci-pipelines
Builds and fixes continuous integration and deployment pipelines — what runs, in what order, how fast, and what blocks a merge. Use this whenever the user is writing a GitHub Actions workflow or other CI config, mentions a slow or flaky pipeline, a failing build, caching, or asks what should run before merge. For the rollout strategy a pipeline deploys with, use agent-deployment for agents or the project's own release process.
- 安装量
- 1
- GitHub Stars
- 2
- 最近更新
- 8月4日
arjunprabhulalincident-response
Runs a live production incident — stabilising first, communicating, and preserving evidence while the system is still on fire. Use this whenever something is broken in production right now, the user mentions an outage, users are affected, a pager fired, or a deploy has gone wrong. This is the during, not the after — for the write-up once it is over, use root-cause-analysis; for a bug that is not currently hurting anyone, use debugging.
- 安装量
- 1
- GitHub Stars
- 2
- 最近更新
- 8月4日
arjunprabhulalinfrastructure-as-code
Defines and changes cloud infrastructure through version-controlled configuration — Terraform, Pulumi, CloudFormation, Kubernetes manifests. Use this whenever the user is writing infrastructure config, mentions Terraform or IaC, needs to provision cloud resources, is dealing with state drift, or is about to click something into existence in a cloud console. For linting existing config, use code-linting.
- 安装量
- 1
- GitHub Stars
- 2
- 最近更新
- 8月4日
arjunprabhulallog-analysis
Extracts an answer from logs, traces, or metrics — finding the relevant lines in volume, correlating across services, and telling signal from noise. Use this whenever the user points at a log file, asks what happened at a particular time, mentions grepping logs, wants to know how often something occurs, or is trying to reconstruct a sequence of events across services. For fixing what the logs reveal, use debugging; for the write-up afterwards, use root-cause-analysis.
- 安装量
- 1
- GitHub Stars
- 2
- 最近更新
- 8月4日
arjunprabhulalroot-cause-analysis
Runs a blameless postmortem after an incident — what broke, why it broke, why it was not caught, and what changes as a result. Use this whenever the user mentions a postmortem, retro, incident review, "five whys", or a root cause analysis, and also when a serious failure has been fixed but never written up. Blamelessness here is a mechanism for getting accurate information, not a courtesy. For the live incident, use incident-response; for finding the cause of a bug, use debugging.
- 安装量
- 1
- GitHub Stars
- 2
- 最近更新
- 8月4日