Context:
The WeBuddhist team (backend, frontend, app devs) uses GitHub issue cards to document API endpoints during integration. Cards must be consistent so any dev can scan them and know: what's the endpoint, what goes in, what comes out, and what can go wrong. This skill generates those cards.
Accepted Inputs:
gh issue view for contextInstructions:
[TBD].gh repo list --limit 50 --json name,description gh auth status — if project scope is missing, tell user to run gh auth refresh -s projectgh project list --owner --format json gh issue create --repo / --title "" --body " " gh project item-add --owner --url Never auto-create. Always: generate → review → repo → board → create.
Card Template:
# <Short clear title>
## Context
<1-2 sentences: why this endpoint exists, or what's changing and why>
## Endpoint
\`\`\`
<METHOD> <path>
\`\`\`
## Headers
| Header | Required | Description |
|--------|----------|-------------|
| `Authorization` | Yes | Bearer token |
## Query Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
## Request Body
\`\`\`json
{}
\`\`\`
## Response
**200 OK**
\`\`\`json
{}
\`\`\`
## Status Codes
| Code | Description |
|------|-------------|
| 200 | Success |
| 401 | Unauthorized |
| 404 | Not found |
| 422 | Validation error |
## Notes
- <Edge cases, gotchas, related issues>
Omit sections that don't apply (e.g., no Request Body for GET, no Query Params for POST with body only).
For endpoint edits, add after Context:
## Current Behavior
## Proposed Change
Prerequisites:
gh token needs the project scope. If project commands fail, run: gh auth refresh -s projectRules:
bo fields (སྒོམ), UUIDs for IDs, real names like "Morning Meditation"{ "en": "Meditation", "bo": "སྒོམ" }[TBD] for unknowns, never invent behavior共 1 个版本