prose-voice
Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | prose-voice |
| description | Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages. |
| user-invocable | false |
Declarative, problem-first, terse.
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…".
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.
Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.
Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.
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".
Clojure style guidelines. Activate before writing or editing Clojure code
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.
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.