prose-voice

Étoiles10

Forks3

Mis à jour30 juillet 2026 à 07:21

Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

SevereOverfl0w

SevereOverfl0w/.files

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	prose-voice
description	Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
user-invocable	false

Declarative, problem-first, terse.

Body

Declarative sentences, present tense, third-person on the code. "This caused…", "These warnings are not helpful…", "Scheduler now supports…". First-person is rare — do NOT default to "I noticed / so I fixed it".
Problem/context first. Lead with the existing behaviour, bug, or motivation; the fix is implicit or trailing. The title describes the problem, the body the why.
Backticks on identifiers, namespaces, specs, paths, test targets.
Cite hard numbers when one exists — "10x speedup", "250ms-450ms in prod", "failed 100 times", CI p95/timeout.
Links inlined in the prose where the rationale sits — NOT collected at the bottom. A bare link as the whole body when that's the rationale of record.

Titles

Imperative mood (bare verb stem, no subject), capitalized first letter, <~100 chars, no prefix, no trailing period. Lead verbs: Like a git commit. E.g. "Add indexes for list-widgets", not "Added…" / "Adds…" / "Adding…".

Real examples

Fix flaky widget Baz generator s/and string? failed 100 times to make a compliant string. Custom generator makes it always happen.

Parallelize Widget Baz lookups Seeing 250ms-450ms times in prod. If 100% of failing widgets are Baz, this adds up.

Suppress BD algorithm warnings Fix https://sentry.io/issues/1234/ - these warnings are not helpful and just spam.

Plus depuis ce dépôt

même dépôt

linear-ticket

SevereOverfl0w/.files

Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.

2026-07-3010

pr-description

SevereOverfl0w/.files

Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.

2026-07-3010

remote-edit

SevereOverfl0w/.files

Hand a file to the user's running editor and block until they finish editing it. Use whenever a draft (PR body, ticket, commit message, any generated file) needs the user's review before you act on it, or when a task says "open this in my editor/vim/nvim".

2026-07-3010

clojure-style

SevereOverfl0w/.files

Clojure style guidelines. Activate before writing or editing Clojure code

2026-07-1610

grill-me

SevereOverfl0w/.files

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.

2026-07-1410

to-issues

SevereOverfl0w/.files

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

2026-07-1410

name	prose-voice
description	Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
user-invocable	false

Declarative, problem-first, terse.

Body

Declarative sentences, present tense, third-person on the code. "This caused…", "These warnings are not helpful…", "Scheduler now supports…". First-person is rare — do NOT default to "I noticed / so I fixed it".
Problem/context first. Lead with the existing behaviour, bug, or motivation; the fix is implicit or trailing. The title describes the problem, the body the why.
Backticks on identifiers, namespaces, specs, paths, test targets.
Cite hard numbers when one exists — "10x speedup", "250ms-450ms in prod", "failed 100 times", CI p95/timeout.
Links inlined in the prose where the rationale sits — NOT collected at the bottom. A bare link as the whole body when that's the rationale of record.

Titles

Real examples

Fix flaky widget Baz generator s/and string? failed 100 times to make a compliant string. Custom generator makes it always happen.

Parallelize Widget Baz lookups Seeing 250ms-450ms times in prod. If 100% of failing widgets are Baz, this adds up.

Suppress BD algorithm warnings Fix https://sentry.io/issues/1234/ - these warnings are not helpful and just spam.