메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | github-issues |
| description | 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. |
Issues and PRDs for this repo live as GitHub issues at leviFrosty/witness-work. Use the gh CLI for all operations — it infers the repo from git remote -v when run inside the clone.
gh issue create --title "..." --body "..." (heredoc for multi-line bodies).gh issue view <number> --comments.gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with --label / --state filters as needed.gh issue comment <number> --body "...".gh issue edit <number> --add-label "..." / --remove-label "...".gh issue close <number> --comment "...".When a skill says "publish to the issue tracker" → create a GitHub issue. "Fetch the relevant ticket" → gh issue view <number> --comments.
Five canonical roles, each mapping directly to a label string in this repo:
| Label | Meaning |
|---|---|
needs-triage | Maintainer needs to evaluate this issue |
needs-info | Waiting on the reporter (repro, questions, screenshots) |
ready-for-agent | Fully specified, ready for an AFK agent |
ready-for-human | Requires human implementation |
wontfix | Will not be actioned |
If a label is missing, recreate it via gh label create rather than inventing a new name.
Full reference (consumed by the engineering skills too): docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md.
How to write a WitnessWork PR description
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).
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.