Run any Skill in Manus with one click

$pwd:

weave-issue

Name: Weave Issue
Author: breferrari

// Create a well-formed GitHub issue for the weave project with all fields populated (labels, type, milestone, assignee, blocked-by relationships). Pass a title and optional description as arguments.

Run Skill in Manus

$ git log --oneline --stat

stars:12

forks:1

updated:March 25, 2026 at 09:13

SKILL.md

readonly

name	weave-issue
description	Create a well-formed GitHub issue for the weave project with all fields populated (labels, type, milestone, assignee, blocked-by relationships). Pass a title and optional description as arguments.
allowed-tools	Bash, Read, Grep, Glob
argument-hint	<title> [--- <description>]

Context

Current branch

!git branch --show-current

Recent commits

!git log --oneline -5

Open issues (for dedup check)

!gh issue list --state open --json number,title --jq '.[] | "#\(.number) \(.title)"' 2>/dev/null | head -20

Available milestones

!gh api repos/PackWeave/weave/milestones --jq '.[] | "\(.title)"' 2>/dev/null

Issue type IDs (for GraphQL)

!gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issueTypes(first: 10) { nodes { id name } } } }' --jq '.data.repository.issueTypes.nodes[] | "\(.name) = \(.id)"' 2>/dev/null

Task

Create a GitHub issue with all fields filled: label, issue type, milestone, assignee, and blocked-by relationships.

Step 1 — Parse arguments

Parse $ARGUMENTS:

Everything before --- (or the entire input if no separator) is the title
Everything after --- is the body/description
If no arguments, ask the user for a title

Step 2 — Classify the issue

Based on the title prefix and content, determine:

Issue type (exactly one):

Bug — title starts with fix: or fix(, or describes something broken
Feature — title starts with feat: or feat(, or describes new functionality
Task — title starts with test:, ci:, docs:, refactor:, chore:, or describes internal work

Label (exactly one):

bug — for Bug type
enhancement — for Feature and Task types
documentation — for docs-only issues

Step 3 — Determine milestone

Ask the user which milestone this belongs to, showing the available milestones from context above. If the user has already specified a milestone in their description, use that. Options:

M6 - 0.5 (security hardening)
M7 - 0.6 (ecosystem depth)
M8 - 0.7 (power features)
None (explicitly deferred)

Step 4 — Check for blockers

Ask: "Does this issue depend on any open issue being completed first?"

If yes, collect the blocking issue numbers
If the user says no or doesn't specify, skip this step

Step 5 — Create the issue

gh issue create \
  --title "<title>" \
  --body "<body>" \
  --assignee $(gh api user --jq .login) \
  --label "<label>" \
  --milestone "<milestone>"  # omit flag entirely if no milestone

Do not create duplicate issues — check the open issues list above first. No "Built with Claude Code" taglines.

Step 6 — Set issue type

Get the new issue's node ID and set the type in a single Bash call (variables don't persist across calls):

NODE_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \
gh api graphql -f query='mutation { updateIssue(input: {id: "'$NODE_ID'", issueTypeId: "<TYPE_ID>"}) { issue { number } } }'

Step 7 — Set blocked-by relationships

If blocking issues were identified in Step 4, for each blocker run in a single Bash call (NODE_ID from Step 6 won't persist — re-fetch it, or chain all steps together):

NODE_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \
BLOCKER_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <BLOCKER_NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \
gh api graphql -f query='mutation { addBlockedBy(input: {issueId: "'$NODE_ID'", blockingIssueId: "'$BLOCKER_ID'"}) { issue { number } blockingIssue { number } } }' && \
gh issue edit <NUMBER> --add-label "blocked"

Repeat for each additional blocker, or loop:

for BLOCKER_NUM in <NUM1> <NUM2>; do
  BLOCKER_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: '$BLOCKER_NUM') { id } } }' --jq '.data.repository.issue.id') && \
  gh api graphql -f query='mutation { addBlockedBy(input: {issueId: "'$NODE_ID'", blockingIssueId: "'$BLOCKER_ID'"}) { issue { number } blockingIssue { number } } }'
done
gh issue edit <NUMBER> --add-label "blocked"

Step 8 — Report

Print a summary:

Created: #<number> <title>
Type:    <Bug|Feature|Task>
Label:   <label>
Milestone: <milestone>
Blocked by: #X, #Y (if any)
URL:     <url>

related-skills.json

same repository

review-prs.md

from "breferrari/weave"

Run multi-persona code review (PO, Senior Eng, Security, Docs) on open PRs. Pass PR numbers or omit to auto-detect from recent branches. Runs 2 rounds by default.

2026-03-2412

weave-e2e.md

from "breferrari/weave"

Run the manual E2E validation checklist against real CLI installations on this machine. Tests weave against actual ~/.claude.json, ~/.gemini/settings.json, ~/.codex/config.toml — not mocks. Pass a flow name to run a targeted subset (install, profiles, search, remove, diagnose), or omit for the full suite.

2026-03-2412

weave-ship.md

from "breferrari/weave"

Full Weave workflow from working changes to open PR. Runs quality gates, commits, pushes, and opens a PR with the correct assignee. Use when ready to ship a change. Pass the commit message as the argument.

2026-03-2212

check-pr-review.md

from "breferrari/weave"

Review all comments and reviews on a GitHub PR — inline code annotations, review verdicts (APPROVED / CHANGES_REQUESTED), and conversation threads. Classifies each as stale/valid/deferred/skip, fixes valid ones in the working tree, creates GitHub issues for deferred ones. Pass a PR number or omit to auto-detect from the current branch.

2026-03-2212

rust-pre-commit.md

from "breferrari/weave"

Run the Weave quality gate (cargo fmt, clippy, tests) before committing. Use when you want to verify the working tree is clean and CI-ready.

2026-03-2212

package.json

"author": "breferrari"

"repository": "breferrari/weave"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

NODE_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \ gh api graphql -f query='mutation { updateIssue(input: {id: "'$NODE_ID'", issueTypeId: "<TYPE_ID>"}) { issue { number } } }'

NODE_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \ BLOCKER_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: <BLOCKER_NUMBER>) { id } } }' --jq '.data.repository.issue.id') && \ gh api graphql -f query='mutation { addBlockedBy(input: {issueId: "'$NODE_ID'", blockingIssueId: "'$BLOCKER_ID'"}) { issue { number } blockingIssue { number } } }' && \ gh issue edit <NUMBER> --add-label "blocked"

for BLOCKER_NUM in <NUM1> <NUM2>; do BLOCKER_ID=$(gh api graphql -f query='{ repository(owner: "PackWeave", name: "weave") { issue(number: '$BLOCKER_NUM') { id } } }' --jq '.data.repository.issue.id') && \ gh api graphql -f query='mutation { addBlockedBy(input: {issueId: "'$NODE_ID'", blockingIssueId: "'$BLOCKER_ID'"}) { issue { number } blockingIssue { number } } }' done gh issue edit <NUMBER> --add-label "blocked"

weave-issue

Context

Current branch

Recent commits

Open issues (for dedup check)

Available milestones

Issue type IDs (for GraphQL)

Task

Step 1 — Parse arguments

Step 2 — Classify the issue

Step 3 — Determine milestone

Step 4 — Check for blockers

Step 5 — Create the issue

Step 6 — Set issue type

Step 7 — Set blocked-by relationships

Step 8 — Report

More from this repository

Context

Current branch

Recent commits

Open issues (for dedup check)

Available milestones

Issue type IDs (for GraphQL)

Task

Step 1 — Parse arguments

Step 2 — Classify the issue

Step 3 — Determine milestone

Step 4 — Check for blockers

Step 5 — Create the issue

Step 6 — Set issue type

Step 7 — Set blocked-by relationships

Step 8 — Report

More from this repository