// Gives you writing style instructions for Explainer type articles including tone of voice, writing style, structure, content formatting and more.
Perform identical, surgical edits across many GitHub repositories without cloning them locally — using the `gh` CLI's Contents API to read files, create branches, commit changes, and open PRs in bulk. Use this skill whenever the user wants to make the same small change (update a README, remove a deprecated badge, fix a link, bump a config) across more than a handful of repos they own or maintain. Trigger this skill on phrases like "across all my repos", "in each of these repos", "bulk update", "open PRs for all of them", "without cloning", "deprecated X in many repos", or any task where the work is mechanically identical and spans 5+ repositories. Even when the user describes the task in domain terms (e.g. "the Snyk badge is deprecated everywhere") rather than "multi-repo edit", trigger this skill — it's the right tool whenever cloning N repos to make a one-line change would be wasteful.
Triage many open GitHub PRs at once — for each PR, check its CI verdict and mergeability, then merge (with admin bypass + squash fallback) or close, in bulk. Use when the user wants to clean up a queue of stale PRs ("close all the old Snyk PRs", "merge anything green and close anything red", "process all the dependabot PRs across my repos") spanning more than a handful of PRs. Trigger on phrases like "go through all my open PRs", "merge or close them all", "clean up the PR backlog", "any PR that's failing CI / unmergeable / stale", or when the user wants the same per-PR decision rule applied to a list of PRs. Sibling skill to `gh-bulk-repo-edit`, but the surface is PR state changes (merge / close / leave), not file contents.
| name | writing-style-explainer |
| description | Gives you writing style instructions for Explainer type articles including tone of voice, writing style, structure, content formatting and more. |
| metadata | {"author":"lirantal","version":"1.1.0"} |
See the writing style JSON definition for tone, structure, density, and formatting defaults.
## References, “Further reading” link dumps, or a bibliography block. Satisfy sourcing by placing ≥3 descriptive inline links to canonical docs, specs, or repos in the body where each topic is introduced or justified.All other explainer guidance (trade-off tables, validation commands, FAQ depth, and so on) still applies unless AGENTS.md or the user says otherwise.