研究检索需要联网github未标认证来源可访问许可证需确认审计通过

ghpm-issue（ghpm 问题）

Agent Skill

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项，并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作；涉及创建 PR、修改 Issue、推送分支或访问私有仓库时，应确认 token 权限、目标仓库范围和用户授权。

总安装

356

周安装

GitHub Stars

下载量

125

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ghpm-issue（ghpm 问题）
来源仓库：https://github.com/jackchuka/ghpm
仓库路径：skills/ghpm-issue
安装命令：
npx skills add https://github.com/jackchuka/ghpm --skill ghpm-issue
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/jackchuka/ghpm --skill ghpm-issue

简介

GHPM 问题技能围绕 GitHub 仓库和协作流程提供辅助能力，提升管理效率。

适用于项目状态查询、变更整理和协作事项管理等开发场景。
通过 GitHub 仓库安装，使用 npx skills add 命令启用技能模块。
涉及创建 PR 或修改 Issue 时需确认 token 权限和仓库访问范围。
ghpm-issue 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

ghpm-issue

PREREQUISITE: Read ../ghpm-shared/SKILL.md for prerequisites and error handling.

File a GitHub issue and add it to the project board in one step. Works mid-session (during ghpm-work) or standalone.

Arguments

/ghpm-issue — interactive: asks for title and body
/ghpm-issue <title> — uses argument as issue title, asks for optional body

Workflow

Phase 1: Setup

Startup sequence: Follow the startup sequence in ../ghpm-shared/SKILL.md. This loads config, refreshes cache if stale, and checks for stale sessions. Extract from config:

- config.project — id, owner, number, title - config.repos — eligible repositories - config.workflow — columns, field_id - config.fields — project fields with name, id, type, options - config.conventions — natural language rules (if present)

Phase 2: Gather Info

Title and body:

- If argument provided, use as title. Ask for an optional body (user can skip). - If no argument, ask for title, then ask for optional body.

Pick repo:

- If config.repos has one entry → use it. - If config.repos is empty or missing → ask the user to specify a repo in owner/repo format. - If config.repos has multiple entries → present a numbered list and ask.

Link to active session: Find active session per ../ghpm-shared/references/session.md (match current branch against session files). If found, prepend to the issue body: Related to <repo>#<num> <original body>

Phase 3: Infer Metadata

All inference is best-effort. Skip silently when no confident match exists.

Infer labels: Fetch the target repo's actual labels: gh label list -R <repo> --json name,description --jq '.[] | "\(.name)\t\(.description)"' Match the issue title and body against the fetched label names and descriptions (case-insensitive substring/keyword matching). Only use labels that exist on the repo — never assume a label exists. If no labels match confidently, skip. Don't force a match.
Infer initial status: Use config.workflow.columns to determine the initial status:

- If config.conventions.status_sync is present, interpret it for new issue context (e.g., if it describes transitions from Planned, that implies new issues start at Planned or earlier). - Otherwise, use the first column in config.workflow.columns as the default. - Never hardcode a column name — always resolve from config.

Infer project fields: Iterate over config.fields entries where type is "single_select" and options is non-empty. For each field, infer the best option from the issue context (title, body, labels, repo name):

- Compare each options[].name (case-insensitive) against the issue context for a substring or keyword match. - If exactly one option matches confidently, use it. If ambiguous or no match, skip silently. - When in doubt, skip rather than guess.

Phase 4: Confirm and Create

Confirm: Prompt (create_issue): Show the resolved issue details — title, repo, labels (if any), initial status, inferred fields — and ask: "Create this issue and add to <project.title>?" Resolve via prompts.ghpm-issue.create_issue per ../ghpm-shared/references/prompts.md.
Create issue: gh issue create -R <repo> --title "<title>" --body "<body>" [--label <labels>] Extract the issue URL from stdout. Then fetch the node ID: gh issue view <url> --json number,url,id --jq '{number:.number, url:.url, nodeId:.id}'
Add to project: gh api graphql -f query=' mutation {addProjectV2ItemById(input: {projectId: "<config.project.id>" contentId: "<issue nodeId>"}) {item {id}}}' Extract the project item ID for field mutations. If this fails: The issue still exists on GitHub. Report the URL and provide the manual fallback: Could not add to project. Add manually: gh project item-add <config.project.number> --owner <config.project.owner> --url <issue-url>
Set status: Using the status resolved in step 6: gh api graphql -f query=' mutation {updateProjectV2ItemFieldValue(input: {projectId: "<config.project.id>" itemId: "<project item ID>" fieldId: "<config.workflow.field_id>" value: {singleSelectOptionId: "<resolved status column id>"}}) {projectV2Item {id}}}' If this fails, continue — the item is on the board, just without a status.
Set project fields: For each field inferred in step 7, set via GraphQL (run mutations in parallel where possible): gh api graphql -f query=' mutation {updateProjectV2ItemFieldValue(input: {projectId: "<config.project.id>" itemId: "<project item ID>" fieldId: "<field.id>" value: {singleSelectOptionId: "<matched option.id>"}}) {projectV2Item {id}}}' If a mutation fails, continue with remaining fields.

Phase 5: Output

Format per ../ghpm-shared/references/format.md: Created #<num> "<title>" in <repo> Project: <config.project.title> (<resolved status>) <field.name>: <option.name> (for each field set in step 12) URL: <issue-url>

Prompt Configuration

Per ../ghpm-shared/references/prompts.md. Config lives at prompts.ghpm-issue in .ghpm/config.json.

Action keys: create_issue.

Tips

This skill does NOT create a work session. Use /ghpm-work <number> after filing to start working on the new issue.

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.54%

按下载量换算47

Claude

32.77%

按下载量换算41

Cursor

17.55%

按下载量换算22

Gemini CLI

9.56%

按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API；具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/jackchuka/ghpm

SKILL.md 来源

github.com

/jackchuka/ghpm/tree/main/skills/ghpm-issue

skills-sh

skills.sh

/jackchuka/ghpm/ghpm-issue

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

ghpm-init（ghpm 初始化）

ghpm-init 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

ghpm-status（ghpm 状态）

ghpm-status 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。