القائمة
Comprehensive management of GitHub Projects (v2). Use to list projects, view items, add items, update fields, and manage project structure in a single skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Technical project manager agent. Use proactively to synchronize repository work with GitHub Project boards.
Expert triage agent. Use proactively to categorize, label, and assign new issues.
Sets the active GitHub project and repository context by writing a repo-level config file at .github/project-config.json. Run once per repository to eliminate repeated context verification prompts and share the context with all team members via git. All subsequent agent sessions will auto-verify silently against this config.
Verifies the current GitHub authentication status and git remote against the repo-level config at .github/project-config.json. Proceeds silently when the environment matches the config. Alerts only when a mismatch is detected or no config exists. Use at the start of every session.
Comprehensive management of GitHub issues, including sub-issue hierarchies. Use to create, update, close, list, search, view, comment on, and manage parent-child relationships between issues in a single skill.
Implements new Agent Skills for the project. Identifies the AI coding tool (Cursor, Claude Code, Gemini CLI), ensures specification compliance, and provides specialized templates. Use when creating, authoring, or adding a new skill, or when the user asks about Agent Skills format or SKILL.md.
| name | gh-project-management |
| description | Comprehensive management of GitHub Projects (v2). Use to list projects, view items, add items, update fields, and manage project structure in a single skill. |
| metadata | {"pattern":"tool-wrapper"} |
Consolidates all GitHub Project (v2) operations into a single, token-efficient skill. This reduces context overhead and simplifies workflows for synchronizing issues with project boards.
gh-verifying-context has been run and confirmed by the user.--owner (user or organization) is specified.Finds the target project and lists its current contents.
Command:
# List projects for an owner
gh project list --owner "my-org" --json number,title,id
# List items in a project
gh project item-list <project-number> --owner "my-org" --json id,title,content
Adds an issue to a project and moves it to a specific status.
Command:
# Add issue to project
gh project item-add <project-number> --owner <owner> --url <issue-url>
# Update a field (e.g., Status)
gh project item-edit --id <item-id> --project-id <project-id> --field-id <field-id> --single-select-option-id <option-id>
Discovers fields and creates draft items.
Command:
# List fields in a project
gh project field-list <project-number> --owner <owner> --json id,name,options
# Create a draft issue
gh project item-create <project-number> --owner <owner> --title "Draft Title" --body "Draft Body"
See references/commands.md for the full action reference table, ID type guide, and list of state-changing commands that require approval.
Always prefer --json for structured data. The internal Item ID (e.g., PVTI_...) is critical for item-edit and item-archive operations, while the Project Number is used for item-list and item-add.