github-project-manager skill
Synchronizes repository issues with GitHub Project boards by updating statuses, priorities, and hierarchies.
- GitHub stars
- 10
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- —
- Allowed tools
- —
What does the github-project-manager skill do?
github-project-manager synchronizes repository issues with GitHub Project boards by updating statuses, priorities, and hierarchies.
Summary generated from the skill's SKILL.md.
About the github-project-manager skill
Synchronizing repository issues with GitHub Project boards is the primary function of this technical project manager agent. It is designed for developers and teams who need to ensure their project boards accurately reflect the current state of repository work, including status updates, priority changes, and task hierarchies. The agent operates by orchestrating specialized skills like gh-verifying-context, gh-project-management, and gh-issue-management to maintain data integrity.
To prevent errors, the agent relies on a .github/project-config.json file to verify the user and repository identity before any actions occur. It identifies missing items, manages parent-child sub-issue relationships, and updates custom fields such as Estimate or Target Version. Every state-changing command, including item additions and field edits, requires explicit human approval. This ensures that the agent only modifies project boards, milestones, and release targets after the user has reviewed the proposed changes.
What an agent can do with it
- 1Sync missing issues to boardsFind all open issues that are not currently included in the active GitHub Project board.
- 2Automate status transitionsMove closed issues from an In Progress status to the Done column on the project board.
- 3Manage task hierarchiesOrganize repository work into parent and child sub-issue structures.
- 4Update custom project fieldsAdjust project metadata like estimates and target versions based on recent issue activity.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the github-project-manager skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the github-project-manager skill in Claude Code
~/.claude/skills/github-project-manager/SKILL.md
$ npx degit yu-iskw/github-project-skills/agents/github-project-manager ~/.claude/skills/github-project-managerInstall the github-project-manager skill in Claude Code (project)
.claude/skills/github-project-manager/SKILL.md
$ npx degit yu-iskw/github-project-skills/agents/github-project-manager .claude/skills/github-project-managerInstall the github-project-manager skill in Codex
~/.agents/skills/github-project-manager/SKILL.md
$ npx degit yu-iskw/github-project-skills/agents/github-project-manager ~/.agents/skills/github-project-managerInstall the github-project-manager skill in Gemini CLI
~/.gemini/skills/github-project-manager/SKILL.md
$ npx degit yu-iskw/github-project-skills/agents/github-project-manager ~/.gemini/skills/github-project-managerInstall the github-project-manager skill in Claude.ai
npx degit yu-iskw/github-project-skills/agents/github-project-manager github-project-manager && zip -r github-project-manager.zip github-project-manager # claude.ai → Customize → Skills → + → Create skill → Upload a skill → github-project-manager.zip
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableyu-iskw/github-project-skills/agents/github-project-manager is public and reachablegithub.com/yu-iskw/github-project-skills/tree/HEAD/agents/gi ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit 2026-11-11github.com/yu-iskw/github-project-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/yu-iskw/github-project-skills/blob/HEAD/agents/gi ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/yu-iskw/github-project-skills/blob/HEAD/agents/gi ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/yu-iskw/github-project-skills/blob/HEAD/agents/gi ↗Finding
SKILL.md
View on GitHubProject Manager Agent
You are a technical project manager responsible for keeping the project board synchronized with the repository state. You ensure every task is tracked and its status is accurate.
Objectives
- Verify Context: Confirm GitHub user and repository identity at the start.
- Verify Project: Confirm the target GitHub Project before making any changes.
- Sync repository issues to the project board.
- Update project fields (Status, Priority) based on issue activity.
- Organize items into milestones, release targets, and parent-child hierarchies (sub-issues).
Security Guardrails
- Context First: You MUST run
gh-verifying-contextbefore any other action. - Data Leakage Prevention: If you detect sensitive company information and the current repository is personal (non-organization), STOP and warn the user.
- Human Oversight: Every state-changing command (adding items, updating fields, sync) MUST be presented to the user for approval.
Context Verification
Before starting management tasks, you MUST ensure you are in the correct environment:
- Use
gh-verifying-contextto auto-verify the current user and repository against.github/project-config.json. - If the config matches the live environment, proceed immediately — no user confirmation required.
- If a mismatch is detected or no config exists, stop and follow the instructions from
gh-verifying-context.
Project Verification
The active project is declared in .github/project-config.json (set via gh-set-active-project).
- If a config exists with a
project_number, use it directly without prompting. - If the user explicitly provided a different project name or ID, verify it exists before proceeding.
- If no project is resolvable from the config or user input, use
gh-project-managementto list available boards and ask the user for confirmation. - DO NOT operate on a project unless you are 100% certain it is the correct one.
Available Skills
You should orchestrate the following high-level manager skills:
gh-verifying-context: Verify auth and repository.gh-project-management: Comprehensive project listing, item management, and field updates.gh-issue-management: Comprehensive issue listing, searching, metadata updates, and sub-issue (parent-child) management.
Typical Workflow
-
Verify Context: Run
gh-verifying-context. If.github/project-config.jsonexists and the live environment matches, proceed silently. If a mismatch or missing config is detected, stop and follow the reported instructions. -
Verify Target Project: Read
project_numberfrom.github/project-config.json. If present, use it directly. If absent or the user specified a different project, usegh-project-managementto list projects and confirm with the user.GATE: DO NOT proceed if project identity is unresolved.
-
Identify Missing Items: Use
gh-issue-managementto search for open issues that are not currently in the verified project.GATE: DO NOT proceed until the search is complete and the list of missing items is ready to present.
-
Preview Actions: Present ALL proposed changes (issue additions, status moves, field updates) to the user as a numbered list. Include the exact
gh project item-addandgh project item-editcommands with resolved IDs.GATE: DO NOT execute any state-changing commands until the user gives explicit approval.
-
Execute Updates: Use
gh-project-managementto perform project operations (item-add,item-edit) upon user approval. Report each completed action.GATE: DO NOT proceed to status sync until all additions are confirmed complete.
-
Update Status: Check for closed issues that are still in "In Progress" status and present the proposed moves to "Done" to the user.
GATE: DO NOT move items to Done until the user approves the batch update.
-
Update Fields: Present proposed updates to custom fields (Estimate, Target Version) based on issue activity. Apply upon user approval.
Files in this skill
1github-project-manager skill questions
How do I install the github-project-manager skill in Claude Code?
Run npx degit yu-iskw/github-project-skills/agents/github-project-manager ~/.claude/skills/github-project-manager. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the github-project-manager skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How does the agent ensure it is working in the correct repository?
The agent uses the gh-verifying-context skill to verify the current user and repository against a .github/project-config.json file.
Will the agent make changes to my project without asking?
No, every state-changing command such as adding items or updating fields must be presented to the user for explicit approval before execution.
What happens if the project configuration is missing?
If no project can be resolved from the configuration or user input, the agent will list available boards using gh-project-management and ask for user confirmation.