원클릭으로
project-github-issues
Create and manage GitHub issues for a multi-repo project, including milestones, project board linking, and sub-issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create and manage GitHub issues for a multi-repo project, including milestones, project board linking, and sub-issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Start one direct background Codex log-monitoring sub-agent that uses non-mutating queries, distills findings for the parent, and never delays the parent's primary task or final response. Resolve log authority from explicit input or the governing AGENTS.md, monitor for at least one real hour at a 60-second cadence, keep clean cycles silent, resume immediately after reports, and ask whether to continue at each hour boundary. Use after runtime changes, when a user asks to check, inspect, tail, watch, or monitor logs, or when independent live-log validation should continue while the parent works.
Run lint/build checks before committing and pushing code, then optionally create a PR via GitHub CLI. Use when a user asks to commit/push changes or requests a pre-push verification workflow.
Sync a local Git repository with its remote safely. Use when an agent needs to update a repo before starting work, fast-forward a local branch from `origin`, confirm that local `main` or another branch matches the remote, or prepare an up-to-date base branch before creating a new branch.
Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.
Plan and run milestone/cycle operations for multi-repo projects in GitHub with a shared milestone per project. Use when defining or revising current/next milestones, deciding cycle load, shaping backlog into AI-ready issues, creating/updating milestones and issues across repos, reviewing GitHub project board health, or producing daily/weekly project execution plans.
Use when the user asks to create a pull request. Build a complete PR using best-practice structure with rich details on changes, verification, QA evidence, risks, and rollout notes. Include issue linkage and clear testing commands/results in the PR body.
| name | project-github-issues |
| description | Create and manage GitHub issues for a multi-repo project, including milestones, project board linking, and sub-issues. |
Use this skill to create well-structured issues across a target set of repositories, add milestones, link to a project board, and create true sub-issues (not just checklist items).
<agent-skills-root>/project-github-issues/SKILL.md).<owner>/<repo-a>, <owner>/<repo-b>, <owner>/<repo-c><board title> (owner: <owner>, project number: <number>)gh issue create and add milestone.Use GraphQL to create true sub-issues.
gh api graphql -f query='query($owner:String!,$name:String!,$parent:Int!,$child:Int!){repository(owner:$owner,name:$name){parent:issue(number:$parent){id} child:issue(number:$child){id}}}' \
-F owner=<owner> -F name=<repo> -F parent=429 -F child=430
gh api graphql -f query='mutation($issueId:ID!,$subIssueId:ID!){addSubIssue(input:{issueId:$issueId,subIssueId:$subIssueId}){issue{number} subIssue{number}}}' \
-F issueId=<PARENT_ID> -F subIssueId=<CHILD_ID>
gh api graphql -f query='mutation($issueId:ID!,$subIssueId:ID!){removeSubIssue(input:{issueId:$issueId,subIssueId:$subIssueId}){issue{number} subIssue{number}}}' \
-F issueId=<PARENT_ID> -F subIssueId=<CHILD_ID>
skill-creator workflow.init_skill.py, edit SKILL.md, then package with package_skill.py.