simpx/loopat/promote

Claude Code and agent skill by simpx/loopat

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Promote this loop's context into shared consensus — the ② edge of docs/context-flow.md. Use when work in a context worktree (notes / knowledge / personal / a repo workdir) is worth sharing, or when the user says promote / share this / publish / sync up / 发布 / 同步 / 合并上去. For notes/personal you merge the latest and push to main; for knowledge you commit and stop (the proposal is reviewed & merged in the Context UI); for repos follow the team's PR flow. You resolve any conflict three-way yourself…

Install

npx vskill@latest install simpx/loopat/promote

SKILL.md

promote — share a loop's context

Promote moves what's worth keeping from this loop into shared main. It is deliberate — do it when the work is genuinely worth sharing, not on every turn. You run plain git; if the merge conflicts, you resolve it yourself (you are the merge agent — no other agent, no script).

Steps

cd into the worktree you want to promote — /loopat/context/notes, /loopat/context/knowledge, /loopat/context/personal, or a repo workdir — then capture your work and merge the latest consensus:

sh
git add -A && git commit -m "<what you're sharing>"
git fetch origin
git merge origin/main

If the merge conflicts, resolve it now, here:

  • Edit each conflicted file; reconcile the <<<<<<< ======= >>>>>>> markers by

keeping both sides' meaning — this is notes/knowledge, so merge the information, don't drop a side.

  • git add the resolved files, then git commit to finish the merge.
  • (git merge --abort backs out cleanly.)

Then land it — how depends on the layer:

sh
# ungated — notes · personal — straight into main:
git push origin HEAD:main
# gated — knowledge — commit and STOP. Do NOT push anywhere:
# your commits wait on this loop's local `loop/<id>` ref as a PROPOSAL;
# the driver reviews & merges them in the Context UI.
# repos — follow the team's flow for that repo (PR, or direct push):
git push origin HEAD
gh pr create --base main --head "$(git symbolic-ref --short HEAD)" --fill

If git push is rejected (non-fast-forward — main moved while you worked), re-run git merge origin/main, resolve again, push again. It converges.

Rules

  • Always merge, never rebase — both parents survive, so a bad merge is

revertible.

  • Resolve conflicts here, yourself — never hand off to another agent.
  • notes / personal push straight to main. knowledge is gated: commit

and stop — never push knowledge main; the proposal is reviewed in the Context UI. Repos follow the team's flow (PR or direct push).

  • Trunk is main (your runtime context block names it if it ever differs).
  • Solo works the same: origin is just a loopat-hosted local repo — same commands.

Security

  • Security scanPassed, 96 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
84
Repository forks
14
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/simpx/loopat/promote/badge)](https://verified-skill.com/skills/simpx/loopat/promote)

Something wrong with this skill or its page? Tell us.