一键在 Manus 中运行任何 Skill

wcc-create-issue

星标10

分支38

更新时间2026年3月19日 13:13

Create a GitHub issue in the Women-Coding-Community/wcc-frontend upstream repository, add it to the Frontend Platform project board, and set Epic, Status, and other project fields. Use when the user asks to create a GitHub issue, ticket, or task for this project.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Women-Coding-Community

Women-Coding-Community/wcc-frontend

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Create GitHub Issue

Create an issue in the upstream repository and add it to the project board with the correct fields set.

Project configuration

Load project-config.md before starting — it contains all field IDs, option IDs, labels, and milestones needed.

Critical: Always use Women-Coding-Community/wcc-frontend as the repo. Never create issues in dricazenck/wcc-frontend (that is the user's fork).

Step 1 — Gather issue details

If $ARGUMENTS was provided, use it as the issue title and ask only for missing required fields. Otherwise ask the user for:

Field	Required	Notes
Title	Yes	Prefix with `feat:`, `fix:`, `chore:`, `docs:` etc.
Body	Yes	Use the template below
Labels	Yes	One or more from project-config.md labels list
Epic	Yes	Choose from Epics table in project-config.md
Status	Yes	Default: `Todo`
Priority	No	Default: none
Size	No	Default: none
Milestone	No	`MVP` or `Phase 2`

Issue body template

## Context

[Why this issue exists and what problem it solves]

## Changes Required

[What needs to be implemented — use bullet points or sub-sections]

## Acceptance Criteria

- [ ] [Criterion 1]
- [ ] [Criterion 2]

## Dependencies

[Other issues or tickets this depends on, if any]

Step 2 — Create the issue

Run gh issue create with all gathered fields:

ISSUE_URL=$(gh issue create \
  --repo Women-Coding-Community/wcc-frontend \
  --title "<title>" \
  --body "<body>" \
  --label "<label1>,<label2>" \
  [--milestone "<MVP or Phase 2>"])
echo "$ISSUE_URL"

Step 3 — Add to project board and set fields

After creating the issue, run these steps in order:

3a — Get the issue node ID

ISSUE_NUMBER=$(echo "$ISSUE_URL" | grep -o '[0-9]*$')
ISSUE_ID=$(gh api "repos/Women-Coding-Community/wcc-frontend/issues/$ISSUE_NUMBER" --jq '.node_id')

3b — Add issue to project

ITEM_ID=$(gh api graphql \
  -f query='mutation($pid:ID!,$cid:ID!){addProjectV2ItemById(input:{projectId:$pid,contentId:$cid}){item{id}}}' \
  -f pid="PVT_kwDOChRKeM4Ahm6k" \
  -f cid="$ISSUE_ID" \
  --jq '.data.addProjectV2ItemById.item.id')

3c — Set project fields

Use this mutation pattern for each field to set. Replace FIELD_ID and OPTION_ID with the values from project-config.md:

gh api graphql \
  -f query='mutation($pid:ID!,$iid:ID!,$fid:ID!,$val:String!){updateProjectV2ItemFieldValue(input:{projectId:$pid,itemId:$iid,fieldId:$fid,value:{singleSelectOptionId:$val}}){projectV2Item{id}}}' \
  -f pid="PVT_kwDOChRKeM4Ahm6k" \
  -f iid="$ITEM_ID" \
  -f fid="<FIELD_ID>" \
  -f val="<OPTION_ID>" > /dev/null

Always set at minimum: Status and Epic. Set Priority and Size only if the user provided them.

Step 4 — Confirm

After all steps succeed, output:

Issue created: <ISSUE_URL>
Added to project board with:
  Epic: <epic name>
  Status: <status name>
  Priority: <priority name or "not set">
  Size: <size name or "not set">
  Milestone: <milestone name or "none">

Error handling

If gh issue create fails: report the error and stop — do not attempt to add to the project
If project mutations fail: report which step failed; the issue already exists and can be added to the project manually
If the user provides an invalid epic/label/milestone name: list the valid options from project-config.md and ask again

同仓库更多 Skills

同仓库

open-pr

Women-Coding-Community/wcc-frontend

Generate a PR title and description following the WCC repo template, infer change types from the diff, and print the GitHub URL to open the PR in the browser. Use when asked to open a PR or create a pull request.

2026-03-2910

commit

Women-Coding-Community/wcc-frontend

Safely commit changes. Reviews staged/modified files for sensitive data, writes a commit message with body. Never adds co-author lines.

2026-03-1910

pr-review

Women-Coding-Community/wcc-frontend

Review pull requests using GitHub CLI. Use when asked to check a PR, perform code review, or leave review comments. Focus on bugs, regressions, security, code quality, best practices, and missing tests; post comments inline on the relevant changed lines and avoid top-level summary comments unless explicitly requested.

2026-03-1910

pre-commit-review

Women-Coding-Community/wcc-frontend

Review local staged and unstaged changes before committing. Outputs an overall summary and per-file line-level findings with severity levels. Use when asked to review code before a commit, check local changes, or suggest improvements on uncommitted work.

2026-03-1910

wcc-smart-issue

Women-Coding-Community/wcc-frontend

Interactively create a well-structured GitHub issue (bug or feature) for Women-Coding-Community/wcc-frontend with Scrum user story, acceptance criteria, test scenarios, and code examples derived from the codebase. Adds the issue to the Frontend Platform project board.

2026-03-1910

name	wcc-create-issue
description	Create a GitHub issue in the Women-Coding-Community/wcc-frontend upstream repository, add it to the Frontend Platform project board, and set Epic, Status, and other project fields. Use when the user asks to create a GitHub issue, ticket, or task for this project.
argument-hint	[title] or describe the issue interactively
allowed-tools	Bash(gh *)

Create GitHub Issue

Create an issue in the upstream repository and add it to the project board with the correct fields set.

Project configuration

Load project-config.md before starting — it contains all field IDs, option IDs, labels, and milestones needed.

Critical: Always use Women-Coding-Community/wcc-frontend as the repo. Never create issues in dricazenck/wcc-frontend (that is the user's fork).

Step 1 — Gather issue details

If $ARGUMENTS was provided, use it as the issue title and ask only for missing required fields. Otherwise ask the user for:

Field	Required	Notes
Title	Yes	Prefix with `feat:`, `fix:`, `chore:`, `docs:` etc.
Body	Yes	Use the template below
Labels	Yes	One or more from project-config.md labels list
Epic	Yes	Choose from Epics table in project-config.md
Status	Yes	Default: `Todo`
Priority	No	Default: none
Size	No	Default: none
Milestone	No	`MVP` or `Phase 2`

Issue body template

## Context

[Why this issue exists and what problem it solves]

## Changes Required

[What needs to be implemented — use bullet points or sub-sections]

## Acceptance Criteria

- [ ] [Criterion 1]
- [ ] [Criterion 2]

## Dependencies

[Other issues or tickets this depends on, if any]

Step 2 — Create the issue

Run gh issue create with all gathered fields:

ISSUE_URL=$(gh issue create \
  --repo Women-Coding-Community/wcc-frontend \
  --title "<title>" \
  --body "<body>" \
  --label "<label1>,<label2>" \
  [--milestone "<MVP or Phase 2>"])
echo "$ISSUE_URL"

Step 3 — Add to project board and set fields

After creating the issue, run these steps in order:

3a — Get the issue node ID

ISSUE_NUMBER=$(echo "$ISSUE_URL" | grep -o '[0-9]*$')
ISSUE_ID=$(gh api "repos/Women-Coding-Community/wcc-frontend/issues/$ISSUE_NUMBER" --jq '.node_id')

3b — Add issue to project

ITEM_ID=$(gh api graphql \
  -f query='mutation($pid:ID!,$cid:ID!){addProjectV2ItemById(input:{projectId:$pid,contentId:$cid}){item{id}}}' \
  -f pid="PVT_kwDOChRKeM4Ahm6k" \
  -f cid="$ISSUE_ID" \
  --jq '.data.addProjectV2ItemById.item.id')

3c — Set project fields

Use this mutation pattern for each field to set. Replace FIELD_ID and OPTION_ID with the values from project-config.md:

gh api graphql \
  -f query='mutation($pid:ID!,$iid:ID!,$fid:ID!,$val:String!){updateProjectV2ItemFieldValue(input:{projectId:$pid,itemId:$iid,fieldId:$fid,value:{singleSelectOptionId:$val}}){projectV2Item{id}}}' \
  -f pid="PVT_kwDOChRKeM4Ahm6k" \
  -f iid="$ITEM_ID" \
  -f fid="<FIELD_ID>" \
  -f val="<OPTION_ID>" > /dev/null

Always set at minimum: Status and Epic. Set Priority and Size only if the user provided them.

Step 4 — Confirm

After all steps succeed, output:

Issue created: <ISSUE_URL>
Added to project board with:
  Epic: <epic name>
  Status: <status name>
  Priority: <priority name or "not set">
  Size: <size name or "not set">
  Milestone: <milestone name or "none">

Error handling

If gh issue create fails: report the error and stop — do not attempt to add to the project
If project mutations fail: report which step failed; the issue already exists and can be added to the project manually
If the user provides an invalid epic/label/milestone name: list the valid options from project-config.md and ask again