メニュー
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in
Boot a live Archie instance from the current branch, drive E2E scenarios headlessly through the archie-debug MCP (nonce → create_task → wait_for_task → approve), capture per-scenario evidence files, and tear down cleanly. Use for Forge Stage 4 QA, verifying a branch against a live instance, running the basic or edit-mode E2E scenario, or when asked to "run the e2e harness", "boot archie for testing", or "verify this AC live".
How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel. Load this when a channel has project context attached (presented to you as channel project context), when part of it is relevant to a teammate, or when it points to a file someone needs.
Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents vs skills vs PM skills. Triggers on "write a plugin", "add an agent", "add a skill", "create a new domain", "make a new teammate". This is the "how to think about it" layer; the README's Plugins section and docs/architecture/plugin-system.md are the "how to wire it up" layer.
Summarize or draft workflow. Use when someone asks to summarize a piece of text, condense a document, draft a short reply, or "TL;DR this". This is the example skill that ships with Archie.
Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can you do", "how do you work", "what are you", "who are you", "are you able to…", "do you have access to…", "can you change yourself", "can you add a plugin", "what's your architecture", "how do you handle…", "what happens when…". Provides the ground truth needed to answer accurately without inventing capabilities.
| name | engineering-pr |
| description | Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework. |
You are managing pull requests for an engineering task. Use these tools and workflows to handle the PR lifecycle.
These tools are available when edit mode is approved:
push_branch(repo_key): Push commits from worktree to origincreate_pull_request(repo_key, title, body): Create PR and register it in taskget_pr_status(repo_key, pr_number): Check PR state and mergeabilityget_pr_reviews(repo_key, pr_number): Fetch reviews and commentsupdate_pr_description(repo_key, pr_number, body): Edit PR descriptionadd_pr_comment(repo_key, pr_number, comment): Add general PR commentadd_review_comment(repo_key, pr_number, path, line, comment): Comment on specific code lineresolve_review_thread(repo_key, pr_number, thread_id): Mark thread resolvedrequest_re_review(repo_key, pr_number): Request reviewers to re-reviewtrigger_merge_check(): Check all linked PRs and merge if ready (approved + CI passing)push_branch(repo_key)create_pull_request(repo_key, title, body) with clear descriptionpost_to_slack notifying user: "I've created a PR with the fix: repo#123"report_completion (this is a user-facing milestone)get_pr_reviews to see detailssend_message_to_agentpush_branch → resolve_review_thread → request_re_reviewadd_pr_comment explaining what was changed (for the GitHub reviewer)get_pr_status shows mergeable: false with mergeableState: dirty → conflicts existsend_message_to_agent: "PR has conflicts with main. Please run git merge origin/main and resolve."push_branchpost_to_slack to confirm completion → report_completionPR review received:
get_pr_reviews for detailsAgent reports fixes complete:
push_branch → resolve_review_thread → request_re_review → add_pr_commentPR merged (system event):
post_to_slack confirming completion → report_completion(message)