メニュー
Skills for working with GitHub Issues. You MUST load this skill when working with issues or when the runtime was triggered by an issue comment. Load this before any gh skills.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agentic-collections --skill github-issueコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | github-issue |
| description | Skills for working with GitHub Issues. You MUST load this skill when working with issues or when the runtime was triggered by an issue comment. Load this before any gh skills. |
| license | MIT |
This skill helps with work on issues.
gh issue.github-pr and gh-pr instead).issues: write permission but needs to modify state.gh issue comment API, polluting the commit history.github.event_name and replying to a PR comment using the
Issue API, causing the response to land in the wrong thread.Upon receiving a new objective, you should focus on the user request first. Identify the trigger source first to understand context and avoid ambiguity. A comment like 'fix it' could refer to a specific issue detail, a previous comment, or a bug report.
Response Detection & Routing:
Check github.event_name and payload to identify trigger source:
issue_comment):
if: ${{ !github.event.issue.pull_request }}gh issue commentRouting Invariants:
Direct API Responses ONLY: When asked to comment on an issue, you MUST use the gh CLI (gh issue comment
etc.) to post the comment directly via API. NEVER write the comment text to a file in the workspace or commit
such files.
For long comments, avoid heredocs as they can cause shell hangs. Write the comment to a temporary file outside the
workspace (e.g., /tmp/comment.md), then use --body-file:
gh issue comment 123 --body-file /tmp/comment.md
Workspace Cleanliness (No Commits for Non-Code-Change Tasks): If your task is purely informational (e.g.,
analyzing an issue, posting a comment), you MUST ensure the workspace remains completely clean (no modified
or untracked files). ANY modification to the workspace after a repo event might trigger unwanted workflows.
Delete temporary files or run git clean -fd before finishing.
Symmetric Routing: ALWAYS reply via the exact originating channel. When asked to post or comment without providing a code fix, you MUST communicate back via the API without modifying any files.
Use github.event.comment.id context to quote or reference the user accurately.
gh issue edit <number>.gh issue close <number> or
gh issue reopen <number> when the issue lifecycle demands it.gh issue view <number> --json comments
Before finishing your session, you MUST ensure the workspace is in a valid state.
If the runtime involved intended modification of files:
If the runtime did not involve intended modification of files:
git status to confirm the workspace is clean.git clean -fd and
git checkout -- ..