update-github-issue-project-status

Update GitHub issue statuses in Projects V2 via GraphQL mutations.

3|Updated Oct 25, 2025

Search Tags:#automation #project management #github #cli #issues #projects #status

Ready to run

npx skills add https://github.com/codekiln/langstar --skill update-github-issue-project-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-github-issue-project-status
Source: https://github.com/codekiln/langstar/tree/main/.claude/skills/update-github-issue-project-status
Command: npx skills add https://github.com/codekiln/langstar --skill update-github-issue-project-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the manual effort of updating GitHub issue statuses (Todo, In Progress, Done) in GitHub Projects V2. It provides programmatic control for single or multiple issues, ensuring your project board accurately reflects progress without tedious clicks.

Core Features & Use Cases

Batch Status Updates: Update the status of single or multiple issues simultaneously in a GitHub Project, streamlining project management.
Issue Assignment: Optionally assign issues to a user when moving them to "In Progress" status, integrating assignment with status changes.
Use Case: After completing a set of tasks, use this skill to mark issues #15, #16, and #17 as "Done" in your project board with a single command, keeping your project status accurate and up-to-date.

Quick Start

Mark issue #17 as "in progress" in the GitHub Project and assign it to codekiln.

Frequently Asked Questions about update-github-issue-project-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate status updates for GitHub issues in Projects V2?▼

Automate status updates by using the gh CLI with GraphQL mutations to transition issues between Todo, In Progress, and Done states in GitHub Projects V2. The Skill handles single or batch updates, eliminating manual project board clicks and keeping your status in sync programmatically.

Can I assign issues to team members while updating their status?▼

Yes, the Skill supports optional assignee assignment when moving issues to In Progress status. It combines status transitions with issue assignments in a single operation, integrating both changes without separate API calls.

What tokens and permissions do I need to update GitHub Project statuses?▼

You need two tokens via environment variables: a project-scoped token (GITHUB_PROJECT_PAT or GH_PROJECT_PAT) for project operations and a repo-scoped token (GITHUB_PAT) for issue assignments. These dual tokens enable full read-write access to both projects and issues.

How do I update multiple issues in a GitHub Project at once?▼

The Skill processes batch updates by accepting multiple issue numbers and applying the same status change across all of them via GraphQL mutations. Pass all issue IDs together to transition them collectively while maintaining individual project item tracking.

Does this work with GitHub Projects V2 only?▼

Yes, the Skill is designed specifically for GitHub Projects V2. It uses the V2 Status field structure and single-select option IDs, which differ from legacy project boards and are not compatible with older project versions.

What happens if an issue isn't already in the GitHub Project?▼

The Skill locates existing project items or creates them if missing, ensuring every issue you target gets added to the project before its status is updated. This handles both existing and newly-added items seamlessly.