メニュー
Creates a GitHub PR for the current work using GitHub MCP; links to an existing issue with Closes
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | pr-from-issue |
| description | Creates a GitHub PR for the current work using GitHub MCP; links to an existing issue with Closes |
Use GitHub MCP (server user-github) for all GitHub actions. Before calling any MCP tool, check its schema (e.g. under mcps/user-github/tools/ or via Cursor MCP discovery) so parameters are correct.
jj bookmark set <branch-name> then jj git push -b <branch-name>..github/PULL_REQUEST_TEMPLATE/ or pull_request_template.md in the repo; use it if present.call_mcp_tool with server user-github and the create_pull_request tool. PR body must include Closes #M.Closes #S1.Closes #S2.Closes #S_last (and any other sub-issues this PR completes) and Closes #M so the main issue is closed when the last PR is merged.Use call_mcp_tool with server: "user-github". Typical tools and intent:
| Tool (check schema for exact name) | Use for |
|---|---|
| get_me | Current user and permissions; infer or confirm owner/repo |
| search_issues | Find existing issue by number, title, or labels; avoid duplicate creation |
| create_issue (or equivalent) | Create main or sub-issue when missing; use issue-refinement-triage labels |
| create_pull_request | Create PR from branch; use repo PR template if present |
| list_issue_types | Optional; use for orgs that use issue types |
Infer owner/repo from git remote or conversation. Always check the tool’s JSON descriptor for required parameters before calling.
This project uses jj. A bookmark is the branch name. Before creating a PR:
jj bookmark set <branch-name> so the bookmark points at the revision to publish.jj git push -b <branch-name>.See jj-bookmark-push for details. Do not rewrite already-pushed commits.
Closes #M (main issue number).Closes #S1 (and any other sub-issues that PR completes).Closes #S_last and Closes #M.Use the repo’s PR template if present. Title and description should reflect the issue and the change.
| Scenario | Action |
|---|---|
| No issue | Create issue via MCP; one PR with Closes #M. |
| One issue, small scope | One PR with Closes #M. |
| One issue, can break down | Create sub-issues S1…Sn; each PR closes its sub-issue(s); last PR closes its sub-issue(s) and Closes #M. |
For when to treat work as "big", how to phrase sub-issues, and example PR body snippets, see reference.md.
Refines GitHub issues using the block template and label table below. Tracking lives on GitHub; use when triaging issues, refining a new issue, or when the user asks to refine an issue.
Checklist for updating project skills when the codebase or workflow changes. Use when applying the skill-maintenance rule, after dependency upgrades or script/e2e/release/issue-format changes, or when the user asks how to keep skills up to date.
Cross-language code quality principles for review and refactors. Use when reviewing structure and naming, applying Kent Beck-style patterns, or when working with the code-quality dev agent. Canonical text lives under .agents/.
Adds or updates extension E2E tests using the project Playwright setup and fixture (load unpacked extension, popup/background). Use when adding e2e for a feature, fixing failing e2e, or when changing popup/options/background flows.
Provides project context for the amgiflol WXT + Svelte 5 browser extension. Use when adding or editing extension code, adding entrypoints, fixing extension bugs, or when working in src/entrypoints or wxt.config.ts.
Uses changesets for versioning and changelog; avoids manual version bumps; aligns with build/zip and workflow_dispatch. Use when cutting a release, adding a changeset, preparing for publish, or when touching version or changelog.