github-voice
Shared writing style rules for GitHub-facing output (PR comments, PR descriptions, PR titles, issues, design proposals).
Checking the letterforms and the sentence
What it does
- No em dashes (—) or double hyphens (--) used as dashes. Use periods, commas, colons, or restructure the sentence. - Write in a natural, human tone.
Read more
Avoid stiff or formal phrasing, unless the session is operating under an explicit style constraint. That constraint governs GitHub text too, and the destination does not relax it. - Don't over-explain. Say what needs saying, then stop. Answer a question with exactly what it asked, in the vocabulary it used. - Leave evidence of correctness out of a PR body: a Verification section and test-count lines when CI runs the suite, and figures from a survey of live data. A statistic offered as reassurance reads as an open question rather than a finished change. Keep a measurement the change exists to produce. - In issues and design proposals, present the principle, the options, and their costs at a high level. Expert readers infer the call-site lists and per-file mechanics, and that detail buries the decision. - When explaining how the code works, describe its current behavior. Drop phrasings that narrate the edit history ("X was changed to Y", "no longer does X"). - When the user has stated their reasoning in the conversation, mine it and
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
No known risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit df43f78 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to tobihagemann/turbo: 2026-10-04 (1 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from tobihagemann
All from this publisher →- apply-findings
Apply findings by making the suggested code changes.
- assess-technical-debt
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot.
- code-style
Enforce existence, reuse, mirror, and symmetry principles to keep new code minimal and consistent with surrounding code.
- codex-exec
Run autonomous task execution using the codex CLI.
- consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving.
