[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75314EPETTH9T09J2GECKSA":3,"skill-same:01M75314EPETTH9T09J2GECKSA":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M75314EPETTH9T09J2GECKSA","standup",null,"Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.","longhang2004\u002FTenvyr","longhang2004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F149140492?v=4","01M752YHWXV1V7TNHCK1P2SNK3","Hàng Nhựt Long","01M752YHYMBBTCMQ391XSES647",0,"MIT","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: standup\nversion: 1.0.0\ndescription: Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.\nallowed-tools:\n  - Bash\n  - Read\n  - Edit\n  - Task\n  - AskUserQuestion\n---\n\n# standup — facilitate a group chat between branch-agents\n\nYou're the **facilitator**. Each of the user's git worktrees (and any PRs they\npick) joins a shared markdown chat as its own agent, and the agents reconcile\ntheir scattered work into ONE consolidated worktree. You convene the room, run\nthe conversation in rounds, and carry the outcome back — the reconciling happens\nin the chat, between the agents.\n\nThe room is one shared file (default `~\u002F.claude-mem\u002FSTANDUP.md`): YAML front\nmatter holds the `goal` + `prompt`; the body is the transcript. Writes are\natomically locked, so agents speak at once. It is **read-only** — agents decide\nhow the merge *should* go; nobody commits or merges inside the room. Real git\nwork happens afterward via `\u002Fdo`.\n\n## 1. Fill the room\n\nTwo ways, mixable:\n\n- **By recency** (common) — worktrees active in a window:\n  ```bash\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" worktrees --since \u003C1h|4h|24h|7d|all> --json\n  ```\n  Active = a commit *or* an uncommitted\u002Fstaged\u002Funtracked edit in the window. If\n  the user didn't name a window, offer 1h \u002F 4h \u002F 24h \u002F 7d \u002F all.\n\n- **By hand** — specific branches and\u002For open PRs:\n  ```bash\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" worktrees --json   # local branches\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" prs --json         # open PRs (via gh)\n  ```\n  Show one numbered list (worktrees + PRs, with age\u002Ftitle); their reply is the\n  \"checkbox.\" If `prs` errors (no `gh` \u002F not GitHub), carry on worktrees-only.\n\nZero or one candidate isn't a standup — say so, offer to widen, stop. Otherwise\necho the roster to confirm before you start.\n\n## 2. Open the room\n\nSet a goal + prompt that invite a conversation, not one-shot status reports:\n\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" open --force --agent facilitator \\\n  --goal \"Collapse these branches\u002FPRs into ONE consolidated worktree: what each changed, where they overlap, which becomes the target, and the merge order.\" \\\n  --prompt \"Facilitated rounds. Round 1: introduce your branch and its state. Then resolve the conflicts the facilitator surfaces, round by round, until the room lands on one concrete plan (target worktree + merge order + conflict resolutions). Read-only: decide, don't merge. Register AGREE when you back the plan.\"\n```\n\n## 3. Run it as rounds\n\nYou drive the turns — if agents watch-loop on their own the room can stall with\nnothing decided. Each agent speaks once per round (read → post → return); you\nread between rounds and bring back whoever's still needed.\n\nSpawned agents don't inherit `CLAUDE_SKILL_DIR`, so resolve it once and paste the\nreal path into each brief:\n```bash\necho \"${CLAUDE_SKILL_DIR}\"\n```\n\n**Round 1 — intros (everyone, one Task message so they run together).** Brief\neach:\n\n> You're **`\u003Cbranch>`** (a PR is **`pr-\u003Cnumber>`**) in a standup group chat. Read\n> `\u003Cskill-dir>\u002Fagent-brief.md` and play your part by it. The room is\n> `~\u002F.claude-mem\u002FSTANDUP.md`; speak with `node \"\u003Cskill-dir>\u002Fstandup.mjs\" post …`,\n> catch up with `… read`. Get your bearings (`cd \"\u003Cpath>\"`,\n> `git log --oneline origin\u002Fmain..HEAD`, `git status --short`,\n> `git diff --stat origin\u002Fmain...HEAD`; a PR uses `gh pr view\u002Fdiff \u003Cnumber>`),\n> then post ONE turn: your branch, its real state, and how it should fold in.\n> Read-only. Then return.\n\n**Reconcile.** Once they've returned, `read` the room and list the **open\nitems** — overlaps, conflicts, competing implementations, undecided\ntarget\u002Forder. None? Skip to the close.\n\n**Resolution rounds (cap ~4).** Per open item, re-spawn only the agents it\nimplicates, with the specific question. Tell them to `read --since \u003Ctheir-name>`\nfirst, then post their position and `--agree` if convinced. `read` again, update\nthe list. Repeat.\n\n**Close — you always write it.** Stop when the list is empty, you hit the cap, or\nan agent errors (note \"didn't report,\" don't block). Then write the SUMMATION\nyourself — don't wait for an agent to volunteer. Write it as plain prose a human\ncan skim, not a field dump: which worktree is the target and why, the merge order\nin a sentence, and what's left for the human:\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" summation --agent facilitator \\\n  --text \"Build on \u003Cworktree> — it's the only one with real code. Layer \u003Cbranch>'s changes on top, then drop in the doc-only branches; skip \u003Cempty branch>. Your call before it's safe: \u003Cthe one or two real decisions>. Done when it all sits in \u003Ctarget> and builds clean.\"\n```\n\n## 4. Brief the human in plain language\n\nThis is the payoff — don't hand them the raw SUMMATION, **translate it.** A human\nwho didn't watch the room should understand the outcome without decoding paths,\nline counts, or commit hashes. Lead with the answer, then the few choices only\nthey can make:\n\n- **What you found** — one plain line per branch: who has real code, who's just\n  docs, who's empty.\n- **The plan** — target + merge order in a sentence or two.\n- **Their call** — only the decisions a human must make (which implementation\n  wins, what to drop, anything risky), as concrete questions. Use\n  `AskUserQuestion` for the clear-cut ones.\n\nKeep git internals out unless they ask. Once they've settled the open calls, hand\nthe plan to **`\u002Fdo`** to perform the merges — don't merge anything yourself\noutside `\u002Fdo`.\n\n## CLI\n\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" \u003Ccommand> [--flags]\n```\nDefaults: agent = git branch, file = `~\u002F.claude-mem\u002FSTANDUP.md`. Every write is\natomically locked.\n\n| command | what it does |\n|---|---|\n| `worktrees [--since 4h] [--json]` | worktrees newest-first; `--since N{m,h,d,w}` keeps those active in the window |\n| `prs [--since 4h] [--json]` | open GitHub PRs (via `gh`) newest-first |\n| `open --goal \"…\" --prompt \"…\" [--force]` | create the room (`--force` rotates an old one aside) |\n| `join [--message \"…\"]` | add yourself + say Hello |\n| `post --message \"…\" [--agree \"…\"]` | append a turn |\n| `agree --deliverable \"…\"` | append an AGREE turn |\n| `watch [--timeout SEC] [--interval SEC]` | block until someone else posts, print it (exit 2 on timeout) |\n| `read [--tail N] [--since AGENT]` | print the chat (or only turns after AGENT's last) |\n| `status` | participants + AGREEs + consensus check |\n| `summation --text \"…\"` | write the SUMMATION, flip `status: agreed` |\n\nEach spawned agent plays its turns by **`agent-brief.md`** (bundled here) — the\nplaybook for being one voice in the room.\n","# standup — facilitate a group chat between branch-agents\n\nYou're the **facilitator**. Each of the user's git worktrees (and any PRs they\npick) joins a shared markdown chat as its own agent, and the agents reconcile\ntheir scattered work into ONE consolidated worktree. You convene the room, run\nthe conversation in rounds, and carry the outcome back — the reconciling happens\nin the chat, between the agents.\n\nThe room is one shared file (default `~\u002F.claude-mem\u002FSTANDUP.md`): YAML front\nmatter holds the `goal` + `prompt`; the body is the transcript. Writes are\natomically locked, so agents speak at once. It is **read-only** — agents decide\nhow the merge *should* go; nobody commits or merges inside the room. Real git\nwork happens afterward via `\u002Fdo`.\n\n## 1. Fill the room\n\nTwo ways, mixable:\n\n- **By recency** (common) — worktrees active in a window:\n  ```bash\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" worktrees --since \u003C1h|4h|24h|7d|all> --json\n  ```\n  Active = a commit *or* an uncommitted\u002Fstaged\u002Funtracked edit in the window. If\n  the user didn't name a window, offer 1h \u002F 4h \u002F 24h \u002F 7d \u002F all.\n\n- **By hand** — specific branches and\u002For open PRs:\n  ```bash\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" worktrees --json   # local branches\n  node \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" prs --json         # open PRs (via gh)\n  ```\n  Show one numbered list (worktrees + PRs, with age\u002Ftitle); their reply is the\n  \"checkbox.\" If `prs` errors (no `gh` \u002F not GitHub), carry on worktrees-only.\n\nZero or one candidate isn't a standup — say so, offer to widen, stop. Otherwise\necho the roster to confirm before you start.\n\n## 2. Open the room\n\nSet a goal + prompt that invite a conversation, not one-shot status reports:\n\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" open --force --agent facilitator \\\n  --goal \"Collapse these branches\u002FPRs into ONE consolidated worktree: what each changed, where they overlap, which becomes the target, and the merge order.\" \\\n  --prompt \"Facilitated rounds. Round 1: introduce your branch and its state. Then resolve the conflicts the facilitator surfaces, round by round, until the room lands on one concrete plan (target worktree + merge order + conflict resolutions). Read-only: decide, don't merge. Register AGREE when you back the plan.\"\n```\n\n## 3. Run it as rounds\n\nYou drive the turns — if agents watch-loop on their own the room can stall with\nnothing decided. Each agent speaks once per round (read → post → return); you\nread between rounds and bring back whoever's still needed.\n\nSpawned agents don't inherit `CLAUDE_SKILL_DIR`, so resolve it once and paste the\nreal path into each brief:\n```bash\necho \"${CLAUDE_SKILL_DIR}\"\n```\n\n**Round 1 — intros (everyone, one Task message so they run together).** Brief\neach:\n\n> You're **`\u003Cbranch>`** (a PR is **`pr-\u003Cnumber>`**) in a standup group chat. Read\n> `\u003Cskill-dir>\u002Fagent-brief.md` and play your part by it. The room is\n> `~\u002F.claude-mem\u002FSTANDUP.md`; speak with `node \"\u003Cskill-dir>\u002Fstandup.mjs\" post …`,\n> catch up with `… read`. Get your bearings (`cd \"\u003Cpath>\"`,\n> `git log --oneline origin\u002Fmain..HEAD`, `git status --short`,\n> `git diff --stat origin\u002Fmain...HEAD`; a PR uses `gh pr view\u002Fdiff \u003Cnumber>`),\n> then post ONE turn: your branch, its real state, and how it should fold in.\n> Read-only. Then return.\n\n**Reconcile.** Once they've returned, `read` the room and list the **open\nitems** — overlaps, conflicts, competing implementations, undecided\ntarget\u002Forder. None? Skip to the close.\n\n**Resolution rounds (cap ~4).** Per open item, re-spawn only the agents it\nimplicates, with the specific question. Tell them to `read --since \u003Ctheir-name>`\nfirst, then post their position and `--agree` if convinced. `read` again, update\nthe list. Repeat.\n\n**Close — you always write it.** Stop when the list is empty, you hit the cap, or\nan agent errors (note \"didn't report,\" don't block). Then write the SUMMATION\nyourself — don't wait for an agent to volunteer. Write it as plain prose a human\ncan skim, not a field dump: which worktree is the target and why, the merge order\nin a sentence, and what's left for the human:\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" summation --agent facilitator \\\n  --text \"Build on \u003Cworktree> — it's the only one with real code. Layer \u003Cbranch>'s changes on top, then drop in the doc-only branches; skip \u003Cempty branch>. Your call before it's safe: \u003Cthe one or two real decisions>. Done when it all sits in \u003Ctarget> and builds clean.\"\n```\n\n## 4. Brief the human in plain language\n\nThis is the payoff — don't hand them the raw SUMMATION, **translate it.** A human\nwho didn't watch the room should understand the outcome without decoding paths,\nline counts, or commit hashes. Lead with the answer, then the few choices only\nthey can make:\n\n- **What you found** — one plain line per branch: who has real code, who's just\n  docs, who's empty.\n- **The plan** — target + merge order in a sentence or two.\n- **Their call** — only the decisions a human must make (which implementation\n  wins, what to drop, anything risky), as concrete questions. Use\n  `AskUserQuestion` for the clear-cut ones.\n\nKeep git internals out unless they ask. Once they've settled the open calls, hand\nthe plan to **`\u002Fdo`** to perform the merges — don't merge anything yourself\noutside `\u002Fdo`.\n\n## CLI\n\n```bash\nnode \"${CLAUDE_SKILL_DIR}\u002Fstandup.mjs\" \u003Ccommand> [--flags]\n```\nDefaults: agent = git branch, file = `~\u002F.claude-mem\u002FSTANDUP.md`. Every write is\natomically locked.\n\n| command | what it does |\n|---|---|\n| `worktrees [--since 4h] [--json]` | worktrees newest-first; `--since N{m,h,d,w}` keeps those active in the window |\n| `prs [--since 4h] [--json]` | open GitHub PRs (via `gh`) newest-first |\n| `open --goal \"…\" --prompt \"…\" [--force]` | create the room (`--force` rotates an old one aside) |\n| `join [--message \"…\"]` | add yourself + say Hello |\n| `post --message \"…\" [--agree \"…\"]` | append a turn |\n| `agree --deliverable \"…\"` | append an AGREE turn |\n| `watch [--timeout SEC] [--interval SEC]` | block until someone else posts, print it (exit 2 on timeout) |\n| `read [--tail N] [--since AGENT]` | print the chat (or only turns after AGENT's last) |\n| `status` | participants + AGREEs + consensus check |\n| `summation --text \"…\"` | write the SUMMATION, flip `status: agreed` |\n\nEach spawned agent plays its turns by **`agent-brief.md`** (bundled here) — the\nplaybook for being one voice in the room.\n",{"name":5,"version":24,"description":7,"allowed-tools":25},"1.0.0",[26,27,28,29,30],"Bash","Read","Edit","Task","AskUserQuestion","main","fa33bab5e066f61f678d15d8654b7f16fcb5aef0",".agents\u002Fskills\u002Fstandup","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr","https:\u002F\u002Fgithub.com\u002Flonghang2004","https:\u002F\u002Flonghang2004.github.io\u002Fportfolio-website\u002F","2026-10-17 00:52:25",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add longhang2004\u002FTenvyr --skill standup",{"tool":44,"command":45},"bunx","bunx skills add longhang2004\u002FTenvyr --skill standup",{"tool":47,"command":48},"pnpm","pnpm dlx skills add longhang2004\u002FTenvyr --skill standup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandup\u002FSKILL.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"agent-brief.md","REFERENCE","参考文档",2173,"https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandup\u002Fagent-brief.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"standup.mjs","SCRIPT","脚本",22168,"https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandup\u002Fstandup.mjs",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M75368XG3WHG7S884RH1FQEG","wowerpoint","Turn one document into a kawaii NotebookLM slide-deck PDF. Use for \"wowerpoint this\", \"make a deck about \u003Cfile>\", \"turn this report into slides\", or any request to render a single document as shareable narrative slides.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fwowerpoint\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7536783K0EKKQ66A56RJ262","what-the","What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-the\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M75362M917THP79D9APYRKTE","weekly-digests","Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for \"weekly digests\", \"week-by-week story\", \"serial timeline\", or \"narrative chapters\" of a project's history.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-digests\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7535ZRATN41PZHPPWZEBM8E","version-bump","Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing (so `npx claude-mem@X.Y.Z` resolves) is handed off to the human maintainer, who raised npm security.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fversion-bump\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7535VQDD9MXAYXH6N2E8FFJ","understand","Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7535T2XNDGZP1GD2AD8VHEW","understand-onboard","Use when you need to generate an onboarding guide for new team members joining a project","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-onboard\u002FSKILL.md",[],[]]