메뉴
File an issue on this repo's GitHub tracker (anandgupta42/receipts) via `gh issue create`. Use when the user asks to file, add, or track an issue for aireceipts. This repo's issues live on GitHub — do not file them into any local or external issue tracker.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Cut an aireceipts release: verify the version tag matches the manifest, generate a changelog from conventional commits, and prep for npm publish (human clicks). Use when the user asks to release, cut a version, or publish a new version.
Adversarially validate a draft spec BEFORE the maintainer sees it. Use after write-spec finishes, or when the user asks to validate/review a spec. A draft without a validation record cannot be approved or built.
Implement an approved spec end-to-end for aireceipts, including agent-team waves for milestone (M-file) specs. Use when the user says implement/build/ship a spec (e.g. 'build SPEC-0001', 'ship M1').
Critically review an aireceipts PR as an independent critic — different model family from whoever built it, audits test-diffs hardest. Use when asked to review a PR, act as the critic, or before landing/merging any change.
Multi-persona release vetting board — PM, EM, Designer, QA personas deeply analyze the release candidate; produces the signed verdict file WITHOUT which /release refuses to proceed. Use before any release, when asked to vet a release, or when cutting a version.
Multi-agent review of user-facing docs (README, docs/**, --help text) for simplicity and correctness. Use before any release, after any feature PR that touched docs, or when asked to review docs.
| name | add-issue |
| description | File an issue on this repo's GitHub tracker (anandgupta42/receipts) via `gh issue create`. Use when the user asks to file, add, or track an issue for aireceipts. This repo's issues live on GitHub — do not file them into any local or external issue tracker. |
| trigger | /add-issue |
aireceipts issues belong on the repo itself: gh issue create -R anandgupta42/receipts
(maintainer directive 2026-07-06). Do NOT file aireceipts issues into local or
external trackers — GitHub Issues is the single source of truth for this repo.
Extract:
gh label list -R anandgupta42/receipts.Public repo — write for a contributor who has no context from your session:
## Problem
<what's wrong, observed behavior, evidence — concrete numbers over adjectives>
## Fix direction
<pointer to the relevant SPEC / module / precedent in this repo, if known>
## Notes
<anything separable: docs-only follow-ups, related-but-distinct observations>
Repo conventions still apply inside issue text: no fabricated numbers, no competitor/inspiration-source comparisons, and any feature-work issue should note that the fix ships with its SPEC-0043 telemetry events + docs parity in the same PR.
gh issue create -R anandgupta42/receipts --title "<title>" --body-file <(printf '%s\n' "<body>")
Prefer --body-file (heredoc or process substitution) over --body so markdown
survives the shell. Add --label flags only for labels verified in step 1.
gh issue view <number> -R anandgupta42/receipts — then give the user the issue
number, title, and URL.