メニュー
How to write a WitnessWork PR description
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
WitnessWork's branching and release workflow — trunk-based on `main`, version bump + release notes via `pnpm run bump-version`, and what each GitHub Actions workflow does. Use when opening a PR, asking which branch to target, cutting a release/version bump, writing release notes, or touching `.github/workflows/*.yml`.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Submit a WitnessWork build to the App Store via the `asc` CLI — create a version, copy metadata, set "What's New", preflight, and submit. Use when releasing to the App Store / TestFlight, cutting a version, pushing release notes, or running App Store Connect operations (versions, metadata, screenshots, pricing, analytics).
Issue/PRD tracking and triage for WitnessWork via the `gh` CLI on leviFrosty/witness-work. Use when creating, reading, listing, commenting on, labeling, or closing GitHub issues, or when applying the repo's triage labels.
How to apply iOS 26 Liquid Glass material in WitnessWork — use `expo-glass-effect`'s GlassView, never hand-build glass from BlurView + opacity. Use when adding/reviewing material on nav bars, tab bars, sheets, primary CTAs, search, or floating overlays, or when you spot a hand-rolled blur/glass surface.
WitnessWork's three-tier feature architecture (app / features / shared) and its lint-enforced import boundaries. Use when adding or moving files, changing import lines, renaming folders under src/, deciding where new code lives, or resolving an eslint-plugin-boundaries violation.
| name | pull-requests |
| description | How to write a WitnessWork PR description |
Keep the description to a minimum, it should be scannable by a reviewer in ~5 seconds. Only expand out the description when the change is extremely non-obviously complicated. Make the PR description only explain how/what and not why, the why will live in the commit message. Only include why if it's not in the commit message and is absolutely necessary for explaining a very very long complex change. It should include functional changes to the behavior or items and not detailed code references to specific files.
At the maximum a description should be no more than 2 paragraphs.
Do not include "Checks/tests" which mention "pnpm typecheck", etc. Only include mandatory non-previously checked human-in-the-loops HITL checks.
Reference existing issues as "fixes #321", "ref #211", etc. by using the /github-issues skill where necessary.
