Skip to content

fix: sub_issue_id に integer database ID を使うようサンプルを修正 #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hirokisakabe merged 2 commits into from
Jun 14, 2026
Merged

fix: sub_issue_id に integer database ID を使うようサンプルを修正 #47

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3beb9b3
fix: use integer database ID for sub_issue_id in skill samples
hirokisakabe Jun 14, 2026
c4877ee
docs: align changed skill versions to 1.0.3
hirokisakabe Jun 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions skills/issue-create/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
name: issue-create
description: "Invoke for any request to create, file, open, or record a new GitHub issue. Trigger on:\n- Direct creation: 「issue 作って」「起票して」「issue 立て(といて)」「issue 化して」「issue 作れる?」\n- Record intent: 「issue に残したい/残しておいてほしい」「issue として残しておきたい」\n- Issue types: bug reports (with repro steps), feature requests, refactoring tasks, doc fixes, code-review findings to track later\n\nDo NOT trigger for viewing, listing, searching, or implementing existing issues."
version: 1.0.2
version: 1.0.3
---

# Issue Create Skill
Expand Down Expand Up @@ -193,13 +193,15 @@ Depends on: #<依存 issue 番号> # 依存がある場合のみ。無ければ
# リポジトリ名を取得
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')

# 子 issue の node ID を取得
CHILD_ID=$(gh issue view "$CHILD_ISSUE_NUMBER" --json id --jq '.id')
# 子 issue の database ID (integer) を取得。
# `gh issue view --json id` は GraphQL node ID (例: `I_kwDO...`) を返すが、
# REST `POST .../sub_issues` の `sub_issue_id` は integer の database ID を要求する。
CHILD_ID=$(gh api "repos/${REPO}/issues/${CHILD_ISSUE_NUMBER}" --jq '.id')

# 親 issue に sub-issue として追加
# 親 issue に sub-issue として追加 (-F で integer として送る)
gh api "repos/${REPO}/issues/${PARENT_ISSUE_NUMBER}/sub_issues" \
-X POST \
-f sub_issue_id="$CHILD_ID"
-F sub_issue_id="$CHILD_ID"
```

7. 紐づけ完了を確認してから、issue URL をユーザーに返す。
Expand Down
8 changes: 5 additions & 3 deletions skills/issue-refine/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
name: issue-refine
description: 既存の GitHub issue を `issue-create` skill のフォーマットに沿って整理する。タイトルのみで起票された issue や、フォーマット不完全な issue を後から rich plan に仕上げ直したい場合に使用する。
version: 1.0.0
version: 1.0.3
---

# Issue Refine Skill
Expand Down Expand Up @@ -82,12 +82,14 @@ EOF

```bash
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
CHILD_ID=$(gh issue view "$ISSUE_NUMBER" --json id --jq '.id')
# 子 issue の database ID (integer) を取得。
# `gh issue view --json id` は GraphQL node ID を返すため、REST endpoint には使えない。
CHILD_ID=$(gh api "repos/${REPO}/issues/${ISSUE_NUMBER}" --jq '.id')
PARENT_ISSUE_NUMBER=<親 issue 番号>

gh api "repos/${REPO}/issues/${PARENT_ISSUE_NUMBER}/sub_issues" \
-X POST \
-f sub_issue_id="$CHILD_ID"
-F sub_issue_id="$CHILD_ID"
```

### 7. 完了報告
Expand Down
Loading