Standardizes change management, impact assessment, and rollback procedures.
Install
mkdir -p .claude/skills/change-management-hack23 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10710" && unzip -o skill.zip -d .claude/skills/change-management-hack23 && rm skill.zipInstalls to .claude/skills/change-management-hack23
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Change management processes, impact assessment, approval workflows, and rollback procedures following ITIL and ISO 27001Key capabilities
- →Document production changes
- →Perform impact assessments
- →Manage approval workflows
- →Plan rollback procedures
- →Ensure ISO 27001 compliance
How it works
It provides a structured process for documenting, assessing, and approving changes to maintain compliance.
Inputs & outputs
When to use change-management
- →Documenting production changes
- →Performing impact assessments for deployments
- →Planning automated rollback procedures
- →Ensuring ISO 27001 compliance for infrastructure
About this skill
Change Management Skill
🔴 AI FIRST Quality Principle
Apply the AI FIRST principle: never accept first-pass quality. Minimum 2 iterations. Read all output, improve every section. No shortcuts.
Purpose
Defines change management processes ensuring controlled, documented changes with proper impact assessment and rollback capabilities.
Change Categories
| Category | Description | Approval |
|---|---|---|
| Standard | Pre-approved, low risk | Automated |
| Normal | Requires assessment | PR review |
| Emergency | Critical fix needed | Post-approval |
Change Process
- Request — Document change and rationale
- Assess — Impact analysis, risk assessment
- Approve — Required reviewers sign off
- Implement — Execute change with monitoring
- Review — Verify change is effective
- Close — Document results and lessons learned
For Static Sites
- All changes via Pull Requests
- CI/CD validates before merge
- Automated rollback via git revert
- Feature flags for gradual rollout
- Monitoring after deployment
Impact Assessment
- Which pages/languages affected?
- Performance impact (Lighthouse check)
- Accessibility impact (WCAG validation)
- SEO impact (structured data, meta tags)
- Security impact (headers, CSP)
Rollback Procedures
- Git revert for code changes
- Previous deployment artifacts cached
- DNS rollback for infrastructure changes
- Communication plan for user-facing changes
ISO 27001 Mapping
- A.8.32 — Change management
- A.8.9 — Configuration management
Related Policies
When not to use it
- →Non-production changes
- →Informal development
Limitations
- →Requires manual compliance checks
- →Requires organizational adoption
How it compares
It integrates ITIL and ISO 27001 standards into the development workflow.
Compared to similar skills
change-management side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| change-management (this skill) | 0 | 4mo | No flags | Advanced |
| secrets-management | 5 | 3mo | Review | Advanced |
| linkerd-patterns | 6 | 5mo | Review | Advanced |
| security-scanning-security-hardening | 3 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Hack23
View all by Hack23 →You might also like
secrets-management
wshobson
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
linkerd-patterns
wshobson
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
security-scanning-security-hardening
sickn33
Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.
github-actions-hardening
locus313
Security hardening reviewer for GitHub Actions workflow files (.github/workflows/*.yml). Reasons about the Actions threat model that pattern matchers and general code linters miss — untrusted-input script injection, privileged triggers running fork code, mutable action references, and over-scoped to
repo-security-posture
superagent-ai
Audit a GitHub repository's security posture and hardening gaps across branch protection, CODEOWNERS, GitHub Actions, publish/release integrity, collaborator access, security features, and dependency review. Use when reviewing or hardening a repo, assessing GitHub configuration, checking CI/CD or Ac
supply_chain_security
zerAda
Docker image signing (Cosign), SBOM generation, SLSA provenance attestation, GHCR registry management.