一键在 Manus 中运行任何 Skill

missive

星标5

分支0

更新时间2026年3月8日 21:57

Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.

安装

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

在 Manus 中运行

来源

justinjdev

justinjdev/fellowship

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

下载

在 Manus 中运行

Missive — GitHub Issue Context

Overview

Fetches structured context from one or more GitHub issues to inform quest planning. Extracts titles, bodies, labels, comments, and produces branch name suggestions and PR close keywords. Designed for both standalone use (display to user) and as input to Gandalf's quest spawning.

When to Use

Before spawning a quest from a GitHub issue
When you need structured issue context for planning
Invoked with /missive #42 or /missive 42 51 67

Input

Accepts one or more GitHub issue references as arguments:

Single: #42 or 42
Multiple: #42 #51 #67 or 42 51 67
Mixed: #42 51 #67

If no arguments are provided, respond with:

"Usage: /missive <issue>... — provide one or more issue numbers (e.g., /missive #42 or /missive 42 51 67)."

Process

Step 1: Parse Issue Numbers

Extract all issue numbers from the args using the pattern #?\d+. Strip any # prefix to get the raw number.

Step 2: Load Configuration

Read ~/.claude/fellowship.json if it exists. Extract:

branch.pattern — branch name pattern with placeholders (default: null, effective: fellowship/{slug})
branch.ticketPattern — regex for ticket extraction (default: [A-Z]+-\d+)
issues.autoClose — whether PRs should auto-close issues (default: true)

If the config file doesn't exist, use all defaults.

Step 3: Verify gh CLI

Before fetching, confirm gh is available:

gh --version

If gh is not installed or not authenticated, respond with:

"The gh CLI is required but not available. Install it from https://cli.github.com/ and authenticate with gh auth login."

Step 4: Fetch Issue Data

For each issue number, run:

gh issue view <number> --json title,body,labels,comments,assignees,milestone

If an issue is not found (non-zero exit), note the error and continue with remaining issues. Do not abort the entire operation for a single missing issue.

Step 5: Build Structured Output

For each successfully fetched issue, produce a structured block:

Context

Title: The issue title
Body: The issue body, truncated to 2000 characters if longer. Append ... [truncated] if truncated.
Labels: Comma-separated list of label names, or "none" if empty
Comments: Up to 5 most recent comments, each truncated to 500 characters. Include author and timestamp. Omit if no comments.
Assignees: Comma-separated list, or "none"
Milestone: Milestone title, or "none"

Branch Suggestion

Resolve the branch name:

If branch.pattern is configured: substitute placeholders per the quest skill's rules, but override {slug} with a slug derived from the issue title (not the task description). The {ticket} placeholder matches branch.ticketPattern against the issue title — if no match, replace with empty string. If {author} is in the pattern but branch.author is not set, replace with empty string. After all substitutions, collapse any resulting double-separators (e.g., // → /, -- → -).
If no pattern configured (default): use fellowship/<number>-<slugified-title> (e.g., fellowship/42-fix-auth-bug). This differs from the quest skill's default (fellowship/{slug}) by including the issue number — linking the branch back to its GitHub issue for traceability.

Slug generation: lowercase the issue title, replace spaces with hyphens, strip non-alphanumeric characters (except hyphens), collapse consecutive hyphens, max 50 characters.

PR Keywords

If issues.autoClose is true (default): Closes #<number>
If issues.autoClose is false: omit the close keyword, note: "Auto-close disabled — link issue manually."

Step 6: Format Output

Output one block per issue in this format:

## Issue #<number>: <title>

### Context
**Labels:** <labels>
**Assignees:** <assignees>
**Milestone:** <milestone>

<body text>

**Recent Comments:**
- [@<author> <timestamp>]: <comment text>
- [@<author> <timestamp>]: <comment text>

### Branch
`<resolved branch name>`

### PR Keywords
`Closes #<number>`

If multiple issues were fetched, output all blocks sequentially.

If any issues failed to fetch, append a summary:

### Errors
- Issue #<number>: <error message>

Key Principles

Fail gracefully. One bad issue number shouldn't block the rest.
Truncate aggressively. Issue bodies and comments can be enormous — cap them to keep context lean.
Config-aware. Respect the user's branch naming and auto-close preferences.
Composable. Output is structured so Gandalf or quest can consume it directly without re-parsing.

同仓库更多 Skills

同仓库

fellowship

justinjdev/fellowship

Multi-task orchestrator. Coordinates agent teammates (led by Gandalf) running /quest (code) or /scout (research) workflows. Use when you have multiple independent tasks to run in parallel.

2026-07-055

quest

justinjdev/fellowship

Use for any non-trivial task. Orchestrates the Research-Plan-Implement cycle with compaction between phases, integrating council, lembas, gather-lore, and warden. Enforces discipline and phase gates.

2026-03-135

retro

justinjdev/fellowship

Post-fellowship retrospective analysis. Collects gate history, palantir alerts, and quest metrics to surface patterns and interactively recommend configuration improvements.

2026-03-125

warden

justinjdev/fellowship

Use AFTER writing code and BEFORE submitting a PR. Simulates a strict code reviewer by comparing changes against reference files and documented conventions. Catches "we don't do it that way" feedback before your human reviewer does.

2026-03-085

scout

justinjdev/fellowship

Research & analysis workflow. Investigates questions, gathers findings, optionally validates with a fresh subagent. Produces a report — no code, no PRs, no commits. Use standalone or as a fellowship teammate.

2026-03-085

council

justinjdev/fellowship

Use at the start of any non-trivial task. Loads focused, task-relevant context by reading CLAUDE.md, scanning for related files, and producing a structured Session Context block. Invoked automatically by quest or standalone via /council.

2026-03-085

name	missive
description	Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.

Missive — GitHub Issue Context

Overview

When to Use

Before spawning a quest from a GitHub issue
When you need structured issue context for planning
Invoked with /missive #42 or /missive 42 51 67

Input

Accepts one or more GitHub issue references as arguments:

Single: #42 or 42
Multiple: #42 #51 #67 or 42 51 67
Mixed: #42 51 #67

If no arguments are provided, respond with:

"Usage: /missive <issue>... — provide one or more issue numbers (e.g., /missive #42 or /missive 42 51 67)."

Process

Step 1: Parse Issue Numbers

Extract all issue numbers from the args using the pattern #?\d+. Strip any # prefix to get the raw number.

Step 2: Load Configuration

Read ~/.claude/fellowship.json if it exists. Extract:

branch.pattern — branch name pattern with placeholders (default: null, effective: fellowship/{slug})
branch.ticketPattern — regex for ticket extraction (default: [A-Z]+-\d+)
issues.autoClose — whether PRs should auto-close issues (default: true)

If the config file doesn't exist, use all defaults.

Step 3: Verify gh CLI

Before fetching, confirm gh is available:

gh --version

If gh is not installed or not authenticated, respond with:

"The gh CLI is required but not available. Install it from https://cli.github.com/ and authenticate with gh auth login."

Step 4: Fetch Issue Data

For each issue number, run:

gh issue view <number> --json title,body,labels,comments,assignees,milestone

If an issue is not found (non-zero exit), note the error and continue with remaining issues. Do not abort the entire operation for a single missing issue.

Step 5: Build Structured Output

For each successfully fetched issue, produce a structured block:

Context

Title: The issue title
Body: The issue body, truncated to 2000 characters if longer. Append ... [truncated] if truncated.
Labels: Comma-separated list of label names, or "none" if empty
Comments: Up to 5 most recent comments, each truncated to 500 characters. Include author and timestamp. Omit if no comments.
Assignees: Comma-separated list, or "none"
Milestone: Milestone title, or "none"

Branch Suggestion

Resolve the branch name:

If branch.pattern is configured: substitute placeholders per the quest skill's rules, but override {slug} with a slug derived from the issue title (not the task description). The {ticket} placeholder matches branch.ticketPattern against the issue title — if no match, replace with empty string. If {author} is in the pattern but branch.author is not set, replace with empty string. After all substitutions, collapse any resulting double-separators (e.g., // → /, -- → -).
If no pattern configured (default): use fellowship/<number>-<slugified-title> (e.g., fellowship/42-fix-auth-bug). This differs from the quest skill's default (fellowship/{slug}) by including the issue number — linking the branch back to its GitHub issue for traceability.

Slug generation: lowercase the issue title, replace spaces with hyphens, strip non-alphanumeric characters (except hyphens), collapse consecutive hyphens, max 50 characters.

PR Keywords

If issues.autoClose is true (default): Closes #<number>
If issues.autoClose is false: omit the close keyword, note: "Auto-close disabled — link issue manually."

Step 6: Format Output

Output one block per issue in this format:

## Issue #<number>: <title>

### Context
**Labels:** <labels>
**Assignees:** <assignees>
**Milestone:** <milestone>

<body text>

**Recent Comments:**
- [@<author> <timestamp>]: <comment text>
- [@<author> <timestamp>]: <comment text>

### Branch
`<resolved branch name>`

### PR Keywords
`Closes #<number>`

If multiple issues were fetched, output all blocks sequentially.

If any issues failed to fetch, append a summary:

### Errors
- Issue #<number>: <error message>

Key Principles

Fail gracefully. One bad issue number shouldn't block the rest.
Truncate aggressively. Issue bodies and comments can be enormous — cap them to keep context lean.
Config-aware. Respect the user's branch naming and auto-close preferences.
Composable. Output is structured so Gandalf or quest can consume it directly without re-parsing.