القائمة
Interact with GitHub via the gh CLI: create issues, pull requests, fetch review threads, post comments, and search. Use when the project's source code hosting or issue tracker is GitHub.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Interact with YouTrack issue tracker via REST API. Create, read, update, and search issues and drafts; manage comments, tags, and issue links; log work items; inspect custom field schemas; list saved queries; look up users and groups. Use when the user asks about YouTrack issues, wants to file bugs, update tickets, add comments, manage tags or links, track time, or search for issues. Requires YOUTRACK_URL and YOUTRACK_TOKEN environment variables.
Authors inline code and diff walkthroughs in IntelliJ IDEA via the walkthrough-plugin MCP tools (show_walkthrough_items, show_diff_walkthrough_items, await_walkthrough_question, insert_walkthrough_tangents). Use when the user asks for a guided tour, walkthrough, explainer, code tour, PR/commit/branch review, or "what changed" anchored to specific files and lines (or diff sides and lines), and the `idea` MCP server is available.
Write structured multi-step implementation plans in markdown format. Plans use numbered steps with clear titles and detailed instructions. Use when asked to create an implementation plan, development roadmap, or multi-step task breakdown.
Generate a narrative story of a PR's changes with embedded code snippets. Use when the user asks to create a PR story, review story, or narrative walkthrough of a pull request's changes.
| name | managing-github |
| description | Interact with GitHub via the gh CLI: create issues, pull requests, fetch review threads, post comments, and search. Use when the project's source code hosting or issue tracker is GitHub. |
| allowed-tools | ["Bash","Read","AskUserQuestion"] |
Set a description and topics for discoverability:
gh repo edit --description "<description>" \
--add-topic "<topic1>" --add-topic "<topic2>"
Add a homepage link if applicable:
gh repo edit --homepage "<url>"
Rename the default branch to main if it is still named master:
# Rename the branch on GitHub (also updates the default branch)
gh api repos/<org>/<repo>/branches/master/rename \
--method POST --field new_name=main
# Update your local clone to track the renamed branch
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
Enable via:
https://github.com/<org>/<repo>/settings/security_analysis
Enable CodeQL with default settings via:
https://github.com/<org>/<repo>/settings/security_analysis
In every GitHub Actions workflow file, add a top-level permissions block with
minimum required access:
permissions:
contents: read
On https://github.com/<org>/<repo>/settings/rules, create a ruleset named
"Protect the main" targeting the default branch with these settings:
Create .github/dependabot.yml with ecosystem-appropriate entries. Example for
Maven/Gradle:
version: 2
updates:
- package-ecosystem: "maven"
directory: "/"
schedule:
interval: "daily"
groups:
all-dependencies:
patterns:
- "*"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
groups:
all-actions:
patterns:
- "*"
Enable Dependabot features via:
https://github.com/<org>/<repo>/settings/security_analysis
Create an issue:
gh issue create --title "<title>" --label "<labels>" --body "<body>"
For long bodies, write to a temp file and use --body-file:
gh issue create --title "<title>" --label "<labels>" --body-file .tmp/issue-body-$RANDOM.md
Search issues:
gh issue list --search "<query>"
gh issue list --label "bug"
Create a PR:
gh pr create --title "<title>" --body-file .tmp/pr-body-$RANDOM.md
Create a draft PR:
gh pr create --draft --title "<title>" --body-file .tmp/pr-body-$RANDOM.md
Include Fixes #<number> in PR body to auto-close the linked issue on merge.
View PR details:
gh pr view <number>
gh pr view --json number --jq '.number'
gh pr diff <number>
Fetch PR comments (paginated):
gh api repos/<org>/<repo>/pulls/<pr>/comments --paginate
Get root-level comments only:
gh api repos/<org>/<repo>/pulls/<pr>/comments --paginate \
--jq '[.[] | select(.in_reply_to_id == null)]'
Fetch review threads with resolution state:
gh api graphql -f query='
{
repository(owner: "<org>", name: "<repo>") {
pullRequest(number: <pr>) {
reviewThreads(first: 100) {
nodes {
isResolved
comments(first: 1) {
nodes {
databaseId
body
author { login }
path
}
}
}
}
}
}
}'
Reply to a review comment:
gh api repos/<org>/<repo>/pulls/<pr>/comments \
--method POST \
--field in_reply_to=<comment_id> \
--field body="<reply text>"
Post an issue comment:
gh api repos/<org>/<repo>/issues/<number>/comments \
--method POST \
--field body="<comment text>"
Avoid shell expansion issues by using a body file:
gh api repos/<org>/<repo>/pulls/<pr>/comments \
--method POST \
--field in_reply_to=<comment_id> \
--field body=@.tmp/reply.txt
The default for any agent-posted review is pending — a draft visible only to the review author until they submit it manually from the GitHub UI. Never use event: COMMENT | APPROVE | REQUEST_CHANGES on the user's behalf without explicit authorization; those values publish the review immediately. Omitting event is what keeps the review pending.
Get the full PR head SHA. Abbreviated SHAs are rejected as "invalid GitObjectID":
gh api repos/<org>/<repo>/pulls/<pr> --jq '.head.sha'
Identify valid lines for inline comments. A comment must anchor to a line inside a diff hunk on the new side (RIGHT); lines in unchanged context between hunks are rejected with "Line could not be resolved". Each hunk header has the form @@ -X[,Y] +A[,B] @@; when a count (,Y or ,B) is omitted, treat it as 1. Valid new-side lines are A through A + (B-1) inclusive:
@@ -10,3 +12,5 @@ → new-side lines 12 through 16@@ -10 +12 @@ → new-side line 12 only (single-line hunk)@@ -10,3 +12 @@ → new-side line 12 onlyGet each file's patch via:
gh api repos/<org>/<repo>/pulls/<pr>/files --paginate
Build the payload. Write it to a body file to avoid shell-expansion issues with backticks or special characters in the comment text:
{
"commit_id": "<full sha>",
"body": "<top-level summary>",
"comments": [
{ "path": "<file>", "line": 42, "side": "RIGHT", "body": "<inline comment>" }
]
}
POST the payload:
gh api -X POST repos/<org>/<repo>/pulls/<pr>/reviews \
--input .tmp/review-$RANDOM.json
Verify the response includes "state": "PENDING". Report the review ID to the user; the draft is visible only to them and does not notify the PR author. They submit it from the GitHub UI (Files changed → Finish your review).
Discard a pending review:
gh api -X DELETE repos/<org>/<repo>/pulls/<pr>/reviews/<review-id>