explain-decision
claudeExplain a decision you have to make, in plain words: the question, why it needs an answer now, each option with its context and cost, a recommendation, and the one line to reply with.
1 skill
Explain a GitHub issue in plain words, with context from the code, the ADRs and the issues it links to, self-contained so you need no follow-up questions: the ask, why it exists as a concrete timeline, where it lands in the code, what is decided, what is still open, how to start.
Plugin explain-issue from marketplace arturblum-skills in Arturblum/skills. Commands read from the repo's manifest — 10 days ago.
explain-issueExplain a GitHub issue in plain words, with the context it needs from the code, the ADRs and the issues it links to. Use when the user gives an issue link or number and asks what it is about.
Explain a decision you have to make, in plain words: the question, why it needs an answer now, each option with its context and cost, a recommendation, and the one line to reply with.
1 skill
Draw a before/after flow diff of a design change as swimlane diagrams: new, changed, removed and unchanged parts in colour, every arrow labelled and numbered, every box explained.
1 skill
Check a GitHub issue before work starts: can it be implemented, what blocks it in the code, the ADRs or open issues and PRs, is the description current, is it still relevant.
1 skill
Review a code change in the order it runs: a guided CodeTour in VS Code with real diffs, one highlighted block per step.
1 skill
Rewrite a GitHub issue's description from the findings of issue-check, and write the still-open design decisions into it. Shows the before and after and asks before it edits.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.