一键在 Manus 中运行任何 Skill

issue-create

星标2

分支2

更新时间2026年6月6日 01:47

Creates GitHub issues with normalized fields, optional metadata, and verification. Use when opening an issue, including optional parent linking.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

nanstey

nanstey/agentic-tools

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Issue Create

Core Contract

Create a GitHub issue with validated fields and verified final state. Use gh by default and infer repo from current remote unless provided. If parent linking is requested, create and verify a real sub-issue relationship. Follow CLAUDE.md / AGENTS.md on conflict.

Required Inputs

Target repository.
Title and body intent (derive from pr-info if missing).
Optional metadata (labels, assignees, milestone).
Optional parent issue reference.
Permission/access constraints.

Workflow

Acquire context (user-provided first; fallback to pr-info derivation).
Resolve repo and permissions.
Normalize payload (title/body + valid optional metadata).
Create issue with gh issue create.
If parent is requested, resolve parent deterministically and create GraphQL sub-issue link.
Verify issue fields and parent linkage with API readback.

If context remains ambiguous, metadata cannot be mapped, or linking fails due to policy/access, stop and ask.

Safety Rules

Never create an issue without confirming minimally sufficient title/body intent.
Never create a placeholder issue from empty context before running pr-info.
Never claim parent linkage succeeded without API-level verification.
Never silently downgrade to a text-only parent reference when real linkage fails.
Never invent labels, assignees, milestones, or parent IDs; validate each explicitly.
Never violate fallback parent ordering in matching fallback mode.
Never use a best-branch fallback parent that has no child issues.
Stop and ask on permission errors, ambiguous repository resolution, or parent mismatch.

Output Style

Report created issue info, context source, applied/skipped metadata, parent selection and linkage result (if requested), verification checks, and any gates encountered.

同仓库更多 Skills

同仓库

prototype

nanstey/agentic-tools

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

2026-07-092

pr-split

nanstey/agentic-tools

Splits a large branch or PR into smaller, independently reviewable units by grouping changes and proposing parallel PRs or a stacked series. Use when a changeset is too big to review well and should be broken up.

2026-07-082

pi-sync

nanstey/agentic-tools

Captures the portable, non-secret pi config from a live ~/.pi/agent into this repo's pi/ directory and commits it, without reading or copying secrets. Use when live pi config or extensions have drifted from the repo and need to be synced back.

2026-07-082

pr-description

nanstey/agentic-tools

Refreshes PR titles and descriptions to match the current branch changeset. Use when the PR title or body has drifted from the code.

2026-07-082

reflect

nanstey/agentic-tools

Reviews the current session for problems and their eventual fixes, then proposes durable improvements to repo skills, scripts, or docs that prevent recurrence. Use when a session hit avoidable friction worth turning into a lasting fix.

2026-07-072

proposal

nanstey/agentic-tools

Runs discovery and uncertainty resolution for a change, then writes a terse plan document covering purpose, behaviour, validation, architecture, and phased vertical slices. Use before building when a change needs a clear, agreed design.

2026-06-252

name	issue-create
description	Creates GitHub issues with normalized fields, optional metadata, and verification. Use when opening an issue, including optional parent linking.
user-invocable	true
disable-model-invocation	false

Issue Create

Core Contract

Required Inputs

Target repository.
Title and body intent (derive from pr-info if missing).
Optional metadata (labels, assignees, milestone).
Optional parent issue reference.
Permission/access constraints.

Workflow

Acquire context (user-provided first; fallback to pr-info derivation).
Resolve repo and permissions.
Normalize payload (title/body + valid optional metadata).
Create issue with gh issue create.
If parent is requested, resolve parent deterministically and create GraphQL sub-issue link.
Verify issue fields and parent linkage with API readback.

If context remains ambiguous, metadata cannot be mapped, or linking fails due to policy/access, stop and ask.

Safety Rules

Never create an issue without confirming minimally sufficient title/body intent.
Never create a placeholder issue from empty context before running pr-info.
Never claim parent linkage succeeded without API-level verification.
Never silently downgrade to a text-only parent reference when real linkage fails.
Never invent labels, assignees, milestones, or parent IDs; validate each explicitly.
Never violate fallback parent ordering in matching fallback mode.
Never use a best-branch fallback parent that has no child issues.
Stop and ask on permission errors, ambiguous repository resolution, or parent mismatch.

Output Style

Report created issue info, context source, applied/skipped metadata, parent selection and linkage result (if requested), verification checks, and any gates encountered.