메뉴
Compact the current conversation into a handoff document for another agent to pick up.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
| disable-model-invocation | true |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
Reference guide for implementing and configuring Comparison Tool (CT) repository classes that extend ComparisonToolRepositorySupport. Use this skill whenever the user is: creating a new CT repository, adding a sort column to an existing CT, debugging unexpected sort order (null rows floating up, wrong column ordering), configuring filters or search for a CT, reviewing a CT repository implementation, or asking how to wire up any part of the CT backend pipeline (sort hooks, filter config, base criteria, spaced field names, heatmap columns, array columns, computed/fallback fields). Trigger phrases include "new CT", "comparison tool", "CT repository", "CT sort", "null rows", "empty rows", "sort order", "heatmap column sort", "array column sort", "getComputedSortFieldExpressions", "getSortFieldAliases", "ComparisonToolRepositorySupport", "CtFilterConfig".
Generates a PR title and description body following repository template standards. Use this skill whenever the user asks to create, write, generate, or update a PR description, or when working with an active pull request that needs documentation. Also use this when the user says things like "write up this PR", "draft the PR", "prepare the PR", or "describe these changes".
Evaluates a proposed version bump for a GitHub Action, reusable workflow, or composite action by comparing the upstream changelog against how the action is actually used in this repo. Use this skill whenever the user mentions bumping, upgrading, updating, or evaluating a version change for anything referenced via `uses:` in `.github/workflows/` *or* `.github/actions/` -- including phrases like "should we upgrade X", "is it safe to bump Y from A to B", "evaluate breaking changes for Z", "Dependabot opened a PR for...", or "what changes between v4 and v7 of...". Trigger even when the user doesn't explicitly say "evaluate" -- if they're asking about the impact of a workflow dependency version change, run this.
Generates monthly update pages for the Sage monorepo documentation site, aggregating all pull requests merged to `main` during a given month into a structured, user-friendly page. Use this skill whenever someone asks for a monthly update, monthly summary, monthly changelog, or wants to create/regenerate the docs page for a specific month — even if they just say "generate the update for March" or "add April to the docs". Trigger on phrases like "monthly update", "monthly summary", "create the update for [month]", "add [month] to the docs", or "regenerate [month-year].md".
Generates standardized weekly updates for the Sage-Bionetworks/sage-monorepo project, summarizing merged PRs, contributor activity, and project progress. Use this skill whenever someone asks for a weekly update, weekly summary, digest of merged PRs, progress report, standup notes, or anything that sounds like a periodic status update for stakeholders — even if they don't explicitly say "weekly update". Trigger on phrases like "what got done this week", "summarize the PRs", "create our weekly digest", "weekly standup summary", or "what did the team ship".
