菜单
Create a GitHub issue/ticket for the Book Corners backend/web repo. Use whenever the user wants to file a bug, create a ticket, open an issue, report a problem, or request a feature/enhancement/documentation change for andreagrandi/book-corners.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Apply Book Corners Django/PostGIS domain knowledge. Use when changing models, migrations, queries, admin behavior, seed data, fixtures, geospatial behavior, slug generation, dependencies, or core library/user app architecture.
Run Book Corners local development commands. Use when starting services, running tests, applying migrations, building CSS, running the dev server, seeding demo data, or building local docs.
Handle Book Corners website UI work and validation. Use when changing Django templates, views, forms, JavaScript, HTMX interactions, static assets, CSS/Tailwind, browser behavior, or user-facing website text.
Update Book Corners API behavior and documentation. Use when changing API endpoints, API schemas, API URL routing, search behavior used by the API, OpenAPI output, or API-facing request/response shapes.
Create Book Corners GitHub issues and add them to the Book Corners GitHub Project. Use when the user asks to add a ticket, create an issue, file a bug, or record an enhancement/documentation work item for this repository.
Handle Book Corners deployment, hosting, production logs, infrastructure, and environment configuration. Use for Dokku, VPS, DNS, SSL, Grafana Loki, production debugging, deploys, rollbacks, backups, or operational commands.
| name | gh-issue |
| description | Create a GitHub issue/ticket for the Book Corners backend/web repo. Use whenever the user wants to file a bug, create a ticket, open an issue, report a problem, or request a feature/enhancement/documentation change for andreagrandi/book-corners. |
Use this workflow to file issues on andreagrandi/book-corners and add them to
the Book Corners project board:
https://github.com/users/andreagrandi/projects/2.
Draft first. Issue creation is outward-facing: show the title, body, labels,
priority, and area, let the user edit, and only run gh issue create after the
user approves. If the description is too thin for a clear Problem and at least
one Acceptance Criterion, ask 1-2 concise questions first. If priority or area
is not stated, ask before creating the issue.
Apply exactly two labels:
book-corners.bug, enhancement, or documentation.Do not invent labels. Area belongs in the project Area field, not labels. Other
repo labels such as dependencies, github_actions, python, docker, or
javascript are not used for new work-item creation unless the user explicitly
requests them.
Verified label IDs are reference-only; pass label names to gh issue create.
| Label | REST ID | Node ID |
|---|---|---|
book-corners | 10998968609 | LA_kwDORXKGvM8AAAACj5bxIQ |
bug | 10274894877 | LA_kwDORXKGvM8AAAACZG50HQ |
documentation | 10274894883 | LA_kwDORXKGvM8AAAACZG50Iw |
enhancement | 10274894891 | LA_kwDORXKGvM8AAAACZG50Kw |
Priority defaults are not allowed in this repo workflow. Ask the user if they did not state priority.
master CI is red.Area is a required project field. Ask the user if it is not stated or inferable.
Use this template unless the user provides a better structure:
## Problem
<What's wrong or missing, and where in the backend/web app>
## Proposed change
<What should happen instead>
## Acceptance Criteria
- [ ] <Done condition 1>
- [ ] <Done condition 2>
Title: short, imperative or problem-focused, with no component prefix.
Optional duplicate check:
gh issue list --repo andreagrandi/book-corners --search "<keywords>" --state open
Create the issue:
URL=$(gh issue create --repo andreagrandi/book-corners \
--title "<title>" \
--body "<body>" \
--label "book-corners" \
--label "<bug|enhancement|documentation>")
Add it to the Book Corners project and capture the item ID:
ITEM_ID=$(gh project item-add 2 --owner andreagrandi \
--url "$URL" --format json --jq .id)
Project ID: PVT_kwHOAAm1584BYNOT
Set Project to book-corners:
gh project item-edit --id "$ITEM_ID" --project-id PVT_kwHOAAm1584BYNOT \
--field-id PVTSSF_lAHOAAm1584BYNOTzhTUrB4 \
--single-select-option-id 1e714f28
Set Priority:
b925d2e023f4e2d289b1cb1egh project item-edit --id "$ITEM_ID" --project-id PVT_kwHOAAm1584BYNOT \
--field-id PVTSSF_lAHOAAm1584BYNOTzhTUrCA \
--single-select-option-id <priority-option-id>
Set Area:
c4e6b87dba5fc05182f936e597b54a1b4ec3ad2e144b587b3aa57aae9574e84egh project item-edit --id "$ITEM_ID" --project-id PVT_kwHOAAm1584BYNOT \
--field-id PVTSSF_lAHOAAm1584BYNOTzhTUrB8 \
--single-select-option-id <area-option-id>
Set Status to Todo:
gh project item-edit --id "$ITEM_ID" --project-id PVT_kwHOAAm1584BYNOT \
--field-id PVTSSF_lAHOAAm1584BYNOTzhTUq48 \
--single-select-option-id f75ad846
Report the issue URL and the selected type, priority, area, and project field.
Only do this when the user explicitly says the issue is blocked by or blocking
another issue. gh has no native issue-dependency command, so use the REST API.
The body uses the other issue's database id, not its #number.
# This issue <N> is blocked by <BLOCKER>.
BLOCKER_ID=$(gh api repos/andreagrandi/book-corners/issues/<BLOCKER> --jq .id)
gh api --method POST -H "X-GitHub-Api-Version: 2026-03-10" \
repos/andreagrandi/book-corners/issues/<N>/dependencies/blocked_by \
-F issue_id="$BLOCKER_ID"
List or remove blocked-by relationships:
gh api repos/andreagrandi/book-corners/issues/<N>/dependencies/blocked_by \
-H "X-GitHub-Api-Version: 2026-03-10" --jq '.[] | "#\(.number) \(.title)"'
gh api --method DELETE -H "X-GitHub-Api-Version: 2026-03-10" \
repos/andreagrandi/book-corners/issues/<N>/dependencies/blocked_by/<BLOCKER_ID>
gh project field-list 2 --owner andreagrandi.gh auth refresh -s project.