菜单
Create and manage GitHub pull requests. Supports both jujutsu (jj) and git version control. Use when submitting PRs, checking PR status, fixing review feedback, or merging PRs. Triggers on "submit pr", "create pr", "check pr", "fix review", "pr status", "merge pr".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Swamp CLI — create and run models, build and validate workflows, query and manage data, store and retrieve vault secrets, develop and publish extensions, initialize repos, run reports, file issues, and troubleshoot errors. Triggers on swamp commands (swamp model, swamp workflow, swamp vault, swamp data), extension development, repo setup, or diagnostic questions. Do NOT use for getting started / onboarding (use swamp-getting-started), pull requests, git operations, worktree management, cron/agent scheduling, or general coding tasks unrelated to swamp.
Interactive getting-started walkthrough for new swamp users. Guides through understanding the user's goals, creating and running a first model, inspecting output, and choosing next steps. Uses a state-machine checklist with verification at each step. Triggers on "getting started", "get started", "new to swamp", "first time", "tutorial", "walkthrough", "onboarding", "how do I start", "what do I do first", "quickstart", "quick start", "hello world", "first model", "just installed swamp", "show me how swamp works", "intro to swamp", "new user", "set up swamp", "learn swamp".
Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues. Use when the user wants to triage a swamp-club issue, generate an implementation plan, or iterate on a plan with feedback. Triggers on "triage issue", "triage #", "issue plan", "review plan", "iterate plan", "approve plan", "issue lifecycle".
Terminal output design system for swamp CLI commands. Use when creating or modifying any CLI command output, render function, or presentation layer code. Ensures consistent formatting, coloring, and structure across all swamp commands in both "log" (human-readable) and "json" (structured) output modes. Triggers on output files in src/presentation/output/, render functions, writeOutput usage, OutputMode handling, or any CLI command that produces terminal output.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Domain Driven Design guidance for TypeScript/Deno codebases. Apply when writing or modifying code to choose appropriate DDD building blocks (entities, value objects, aggregates, domain services, repositories) and maintain ubiquitous language. Triggers on all code changes to ensure domain model consistency.
| name | github-pr |
| description | Create and manage GitHub pull requests. Supports both jujutsu (jj) and git version control. Use when submitting PRs, checking PR status, fixing review feedback, or merging PRs. Triggers on "submit pr", "create pr", "check pr", "fix review", "pr status", "merge pr". |
First, determine which version control system is in use:
if [ -d ".jj" ]; then
echo "jujutsu"
else
echo "git"
fi
.jj exists: Read references/jujutsu.md for
VCS-specific commandsRun these checks before submitting any PR:
deno fmt --check
deno lint
deno run test
Fix any issues before proceeding. All checks must pass.
If deno fmt --check fails, run deno fmt to auto-fix formatting, then re-run
the checks.
After pushing changes (see VCS reference), create the PR:
gh pr create --head <branch-or-bookmark> --base main --title "Title here" --body "$(cat <<'EOF'
## Summary
Brief description of changes.
## Test Plan
- How the changes were tested
EOF
)"
To check if a PR is ready to merge:
# Check CI status
gh pr checks <pr-number>
# View PR details including review status
gh pr view <pr-number>
When a PR has blocking review feedback:
Get the review comments:
gh pr view <pr-number> --comments
Enter plan mode to analyze the feedback and plan fixes
Implement the fixes
Push updates (see VCS reference for push commands)
Re-request review if needed:
gh pr edit <pr-number> --add-reviewer <username>
When reviewers provide non-blocking suggestions:
Get suggestions from the review:
gh pr view <pr-number> --comments
Enter plan mode to evaluate each suggestion
Decide which suggestions to implement (discuss with user if unclear)
Implement approved suggestions and push
Respond to suggestions you chose not to implement with reasoning
Once all checks pass and reviews are approved:
# Squash merge (preferred)
gh pr merge <pr-number> --squash --delete-branch
# Or merge commit
gh pr merge <pr-number> --merge --delete-branch