Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

github-issues-task-management

Étoiles3

Forks0

Mis à jour29 avril 2026 à 01:45

This skill should be used when organizing work via GitHub Issues and Projects, creating project boards, managing milestones, or when consolidating fragmented tracking into GitHub-native tracking. Trigger phrases: "set up projects", "create a project board", "organize issues", "milestone planning", "what issues need attention", "consolidate tickets".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

nsheaps

nsheaps/ai-mktpl

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	github-issues-task-management
description	This skill should be used when organizing work via GitHub Issues and Projects, creating project boards, managing milestones, or when consolidating fragmented tracking into GitHub-native tracking. Trigger phrases: "set up projects", "create a project board", "organize issues", "milestone planning", "what issues need attention", "consolidate tickets".

GitHub Issues Task Management

GitHub Issues and Projects are one concrete implementation of project-management tracking. This skill covers the methodology for using GitHub as the canonical system for tracking work items, milestones, and project status.

Core Principles

GitHub Issues are canonical. Every significant work item needs a GitHub Issue. If it is not in GitHub Issues, it is not tracked.
Consolidate, don't fragment. Prefer fewer, broader issues over many narrow ones. A single issue for "implement feature X" is better than five issues for each sub-task unless the sub-tasks will be worked independently by different people or across different PRs.
Communication channels supplement, not replace. Real-time channels (chat, threads) are for discussion, status pings, and coordination. The issue is where decisions, acceptance criteria, and resolution are recorded.
Link everything. PRs link to issues. Issues link to project boards. Cross-repo references use full owner/repo#N format.

Issue Lifecycle

Creating Issues

Every issue must have:

Clear title -- action-oriented, specific (not "Fix stuff")
Body with context -- what, why, and acceptance criteria
Labels -- at minimum a type label

Use the issue-management skill for the mechanics of creating, searching, and updating issues via gh CLI. This skill covers the methodology.

Linking PRs to Issues

Add magic phrases to the PR body to auto-close issues on merge:

Fixes #42
Fixes nsheaps/ai-mktpl#15
Closes #7

Semantic convention (GitHub treats all linking keywords identically, but we use them to signal intent to human readers):

Fixes -- the PR satisfies/resolves the issue described (bug fix, feature implementation). The issue represents work that is now complete.
Closes -- the PR supersedes or replaces another PR or issue without necessarily implementing it (e.g., a rewrite that obsoletes an older PR, or closing a duplicate).

For cross-repo links, always use the full owner/repo#N format.

Closing Issues

Issues close automatically when a linked PR merges. If closing manually, always include a comment explaining resolution and referencing the relevant commit or PR.

Labels

Labels vary by project. Always conform to whatever the project's .github/labels.yaml defines as the single source of truth. The categories below are common conventions.

Priority Labels

Common conventions include p0/p1/p2/p3 or priority:high/priority:low. Check the project's .github/labels.yaml for the actual label names and use those.

Concept	Meaning
Critical	Blocking all other work, fix immediately
High	Should be resolved this sprint/cycle
Normal	Important but not urgent
Low	Nice to have, backlog

Type Labels

Common type labels (exact names may differ per project):

Concept	Meaning
bug	Something is broken
enhancement	Improvement to existing functionality
chore	Maintenance, refactoring, tooling
question	Needs discussion or clarification

Status Labels (optional)

Use sparingly -- GitHub Projects board columns often replace these:

Concept	Meaning
needs-triage	Not yet prioritized
blocked	Waiting on external dependency
in-progress	Actively being worked

GitHub Projects

When to Use Projects

Organizing work across multiple repos
Tracking milestones with multiple constituent issues
Providing stakeholder visibility into progress
Sprint or cycle planning

Project Board Setup

# Create a project (org-level)
gh project create --owner nsheaps --title "Milestone: Feature X"

# Add an issue to a project
gh project item-add PROJECT_NUMBER --owner nsheaps --url https://github.com/nsheaps/repo/issues/42

Board Columns

Standard column layout:

Column	Purpose
Backlog	Triaged but not started
In Progress	Actively being worked
In Review	PR open, awaiting review
Done	Merged and verified

Consolidation Strategy

When transitioning from fragmented tracking to consolidated GitHub tracking:

Step 1 -- Audit existing issues

gh issue list --repo owner/repo --state open --limit 100

Step 2 -- Identify duplicates and related issues

Group issues that track the same feature, bug, or initiative. Look for:

Same root cause described differently
Sub-tasks that belong under a parent issue
Issues that were superseded by newer ones

Step 3 -- Consolidate

Close duplicates with a comment linking to the canonical issue
Merge sub-tasks into a parent issue (add as checklist items in the body)
Transfer context from communication channels into issue comments

Step 4 -- Organize into project

Create or update the relevant GitHub Project board
Add all canonical issues to the board
Set priorities and assignments

Cross-Repo Issue Linking

When work spans multiple repos, always use full references:

Related to nsheaps/agents#12
Blocked by nsheaps/ai-mktpl#45
Fixes nsheaps/ai-mktpl#15

Short references (#N) only work within the same repo. Cross-repo references require owner/repo#N.

Relationship to Other Skills

Skill / Rule	Scope
`issue-management`	Mechanics: how to create, search, update, close issues via CLI
`github-issues-task-management` (this skill)	Methodology: how to organize work, manage projects, consolidate tracking
`agentic-behavior/rules/work-tracking.md`	Abstract linking and milestone rules (platform-agnostic)

Anti-Patterns

Anti-Pattern	Instead
Tracking work only in chat threads	Create a GitHub Issue; use chat for discussion
One issue per tiny sub-task	Consolidate into a parent issue with a checklist
Short-form references across repos (`#N`)	Use `owner/repo#N` for cross-repo links
No labels on issues	Add at least type + priority labels
Closing issues without explanation	Comment with resolution and link to PR/commit
Using issue body as a living document without history	Use comments for updates; keep body as canonical state

References

Plus depuis ce dépôt

même dépôt

nsheaps-claude-marketplaces

nsheaps/ai-mktpl

Use this skill to understand the claude marketplaces in the nsheaps github org: the plugin marketplace build, release, and propagation pipeline. Recall this skill when working on CI/CD workflows, mise tasks, plugin versioning, marketplace updates, or when asked how plugins get from source code to a user's Claude Code installation. Also recall when debugging version bumps, marketplace.json drift, or plugin cache issues.

2026-06-093

nsheaps/ai-mktpl

Use this skill when the user asks about GitHub operations, pull requests, issues, releases, actions, gists, repos, or any task involving the GitHub CLI (gh). Also use when needing to interact with GitHub APIs, check CI status, review PRs, manage labels, create releases, or automate GitHub workflows from the command line.

2026-06-093

github-app-git-identity

nsheaps/ai-mktpl

Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>

2026-06-083

github-app-session-env

nsheaps/ai-mktpl

Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>

2026-06-083

github-app-token

nsheaps/ai-mktpl

Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>

2026-06-083

spec-management

nsheaps/ai-mktpl

Manages spec files for requirements capture and validation

2026-06-063