메뉴
Copy a project-board issue into the fragalysis-backend repo. Use when the user asks to create a backend issue from a project-board issue, e.g. "Create an issue for project issue 1234".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-backend-issue |
| description | Copy a project-board issue into the fragalysis-backend repo. Use when the user asks to create a backend issue from a project-board issue, e.g. "Create an issue for project issue 1234". |
Copy an issue from the m2ms project board
(https://github.com/orgs/m2ms/projects/2) into this project's repository
(xchem/fragalysis-backend).
Trigger phrases such as:
The number the user gives is the project-board issue number.
Given a project-board issue number, the skill:
m2ms/fragalysis-frontend (the board's planning
issues live there).fragalysis-backend label. If it does
not, it stops and reports — nothing is created.xchem/fragalysis-backend with the same title
and a copy of the body (plus a footer linking back to the source).It is idempotent: a hidden marker is written into the comment, so running it twice for the same issue refuses to create a duplicate.
Run the helper script with the project-board issue number:
.claude/skills/create-backend-issue/create-backend-issue.sh <project-issue-number>
For example, for "Create an issue for project issue 1234":
.claude/skills/create-backend-issue/create-backend-issue.sh 1234
On success it prints the source URL and the new backend issue URL — relay both to the user. On any error it exits non-zero and prints the reason to stderr; report that reason rather than retrying blindly.
gh CLI (authenticated, with repo scope) and jq. No GitHub
project scope is needed because the issue is resolved by repository, not by
querying the board API.m2ms/fragalysis-frontend. This is safe because
the fragalysis-backend label only exists in that repo, so any board issue
carrying it lives there. If the board's planning issues ever move to another
repo, update SOURCE_REPO in create-backend-issue.sh.Build a developer Fragalysis Stack (backend + stack container images) and then deploy it to Kubernetes by triggering the developer's AWX Job Template
Work on a GitHub issue end-to-end in a git worktree — move its board card to In Progress first, read the issue, explore the code, branch from staging, write the test first (TDD), commit, and open a PR. Use when the user says e.g. "work on issue 958", "start issue 1234", "/issue N", or asks to take a fragalysis-backend issue from triage to PR.
Release the staging branch to production. Opens a staging→production PR, waits for CI, merges it (keeping staging), then publishes a YYYY.MM.ITERATION GitHub release of production. Use when the user asks to "release staging", "do a release", or "release the staging branch".
Finalise a Release ticket on the m2ms Fragalysis project board — move every "fragalysis-backend"-labelled issue from the "Approved in staging - push to production" swimlane into "In production (Done)" and list them on the Release ticket. Use after a staging→production release, when the user says e.g. "finalise release 2246", "mark release 2246 done", "move the approved backend issues to production for release 2246".