メニュー
Sync the shared knowledge vault by committing local `context/` changes, rebasing onto the latest `main`, resolving context conflicts, and pushing back to origin.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill when exploring a fuzzy idea, thinking through a concept from first principles, stress-testing assumptions, or crystallizing what you're actually trying to build before committing to a plan. Load when asked to brainstorm, when a problem statement is vague, or when the user is saying "I'm thinking about..." rather than "build this."
Use this skill when verifying that implementation work meets acceptance criteria, reviewing code for security vulnerabilities, assessing code quality and stability, or producing a formal review report. Load when conducting QA, security audits, or acceptance testing against a defined spec.
Use this skill when verifying a build, preparing a deployment, creating pull requests, running health checks, or managing a release. Load when the task is to get code from "merged" to "running in production" — or to confirm it is ready to be merged.
Use this skill when writing implementation plans, spec files, or step-by-step execution plans for engineers or sub-agents. Load when translating an architecture document and requirements into a concrete, ordered execution plan where each step must be self-contained and independently executable.
Use this skill when writing product requirements documents, defining acceptance criteria, or translating research and user needs into structured, testable specifications. Load when the task is to define what the system must do — not how — including functional requirements, non-functional requirements, user stories, acceptance criteria, and scope boundaries.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
| name | sync-brain |
| description | Sync the shared knowledge vault by committing local `context/` changes, rebasing onto the latest `main`, resolving context conflicts, and pushing back to origin. |
Use this skill when the user wants to sync shared knowledge in $HOME/workspace/context/ with the remote repository.
Safely update origin/main with local knowledge changes from context/ while keeping the branch rebased on the latest remote history.
$HOME/workspace.main before syncing.context/.context/ that belong in durable knowledge.context/ changes if there is anything to commit.git fetch origin.git pull --rebase origin main.context/, resolve them by merging both sides carefully:
updated datemain branch to origin.context/ unless the user explicitly asks.context/, stop and ask the user instead of guessing.context/ changes, skip the commit and just sync with remote.context: sync brain updates unless the user provides one.cd ~/workspace
git checkout main
git add context
git commit -m "context: sync brain updates"
git fetch origin
git pull --rebase origin main
# resolve conflicts if needed
git push origin main
Adapt the exact commands to the repo state. For example, skip the commit when context/ has no changes, and avoid re-staging unrelated files.
When a markdown note in context/ conflicts:
updated field after resolving the noteIf the conflict cannot be resolved confidently without changing meaning, ask the user with a short explanation of the tradeoff.