Read recent releases from CHANGELOG.md and display their version numbers, dates, and complete change sections. Choose how many entries to show, or view the full history while preserving the document’s formatting.
View recent CHANGELOG entries
Review the instructions the agent will receive before you install.
Use this skill when the user asks to run the migrated source command changelog.
Display recent entries from CHANGELOG.md with optional count limit.
/changelog # Show last 5 entries (default)
/changelog 10 # Show last 10 entries
/changelog all # Show all entries
Read CHANGELOG.md and extract the last N version entries with:
📋 Recent CHANGELOG Entries
═══════════════════════════════════════════════════════════
## [3.9.11] - 2026-01-20
### Added
- Production Safety Rules (Section 14.3)
- Critical safety practices for production deployments
- Rollback procedures and monitoring guidelines
### Documentation
- Enhanced deployment workflow documentation
- Added safety checklist templates
═══════════════════════════════════════════════════════════
## [3.9.10] - 2026-01-19
### Added
- DevOps & SRE Guide with FIRE Framework
- Fault tolerance patterns
- Incident response protocols
- Recovery procedures
- Escalation guidelines
### Documentation
- New Section 9.18: DevOps & SRE Practices
- 45+ operational best practices
═══════════════════════════════════════════════════════════
[... more entries ...]
───────────────────────────────────────────────────────────
Showing 5 of N total entries
Use /changelog 10 for more, or /changelog all for complete history
## \[(\d+\.\d+\.\d+)\] - (\d{4}-\d{2}-\d{2})[Unreleased] section if present at topNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.