yonatangross/orchestkit
Overview
This skill visualizes planned code and architecture changes before they are applied, producing structured ASCII diagrams, risk analysis, execution swimlanes, and impact metrics. It helps reviewers and engineers quickly assess scope, reversibility, and the critical path so teams can make informed decisions before merging or deploying.
How this skill works
The skill auto-detects plan context from the current branch or a provided issue, then runs analysis scripts to collect file diffs, line counts, test impact, and dependency changes. It renders a Tier 1 header followed by requested sections: change manifest, execution swimlane, risk dashboard, decision log, and impact summary, with options to save reports or generate GitHub issues.
When to use it
- Before opening or merging a pull request that affects multiple modules
- When comparing before/after architecture for high-risk changes
- To assess reversibility and identify the point of no return for migrations
- While planning phased deployments to surface execution dependencies
- When preparing reviewers or release notes with actionable artifacts
Best practices
- Run auto-detection first; clarify context only if detection is ambiguous
- Always show the Tier 1 header to surface risk, confidence, and reversibility
- Flag high-risk files and provide concrete mitigations in each pre-mortem
- Document only non-obvious decisions and include rejected alternatives
- Keep visualizations judgmental (what matters) rather than decorative
Example use cases
- Visualize a multi-phase database migration with rollback points and critical path
- Compare current branch changes for a billing redesign and list affected tests
- Produce a deployment swimlane that shows blocked work, parallel opportunities, and estimated times
- Generate a concise impact summary for a release note or audit
- Create GitHub issues from execution phases with risk labels and blocked-by links
FAQ
Risk is computed from the highest-risk file or phase (uncovered critical paths, deletions, or breaking API changes) combined with test coverage and dependency churn to report LOW/MEDIUM/HIGH/CRITICAL.
Can I save the report or create issues automatically?
Yes — the skill can write designs/{branch}.md using the report template and generate GitHub issues per execution phase with labels, milestones, and blocked-by references.
11 skills
This skill visualizes planned changes as ASCII diagrams with risk, execution order, and impact metrics to inform review.
This skill helps you implement comprehensive monitoring and observability patterns for Prometheus, Grafana, Langfuse tracing, and drift detection.
This skill helps you discover and navigate OrchestKit's available skills and categories with an interactive guide.
This skill creates validated conventional commits locally, ensuring branch safety, linting, and concise messages before pushing.
This skill orchestrates parallel agents to turn rough ideas into robust design options through structured, multi-phase brainstorming and evaluation.
This skill helps you create polished demo videos for skills, tutorials, and CLI demos with templated, multi-format outputs.
This skill orchestrates memory graph queries to extract, deduplicate, and boost cross-referenced memories for unified context.
This skill performs comprehensive health checks on OrchestKit installations, diagnosing plugin, hook, memory, and coordination health for faster
This skill coordinates multiple Claude Code worktrees, enabling synchronized status, file locking, and conflict checks across parallel sessions.
This skill analyzes error patterns from Claude Code sessions to deliver actionable fixes and root-cause insights.
This skill helps assess task complexity, enforce quality gates, and guide escalation to prevent wasted work and unclear requirements.
