[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7ZDKBX2WZ3RGZE2W2YTHX":3,"skill-same:01M7F7ZDKBX2WZ3RGZE2W2YTHX":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7F7ZDKBX2WZ3RGZE2W2YTHX","reflect",null,"Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.","bitgineer\u002Fopencode-pstack","bitgineer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F133060368?v=4","01M7F7V139SDYHXSH9GXXM8EV7","01M7F7V13Y1ZZCY3J922JX06QC",1,"MIT","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: reflect\ndescription: Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.\n\n---\n\n# Reflect\n\nMine the current conversation for durable learnings, then route them into skill edits.\n\nInvoke when the user says \"reflect\" or \"\u002Fpstack\u002Freflect\". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.\n\n## 1. Locate the active transcript\n\nBefore fanning out, find this conversation in the session store. `opencode session list` prints recent sessions with their IDs and working directories. Take the one whose directory matches this workspace and whose opening user prompt is this conversation's. Export it to read it. Do not list or export sessions from other projects. That crosses workspace boundaries and reads private chats from unrelated projects.\n\n```bash\nopencode session list\nopencode session export \u003CsessionID>\n```\n\nThe database behind both is `~\u002F.local\u002Fshare\u002Fopencode\u002Fopencode.db`. For each candidate, match the first user message against the conversation's opening prompt. If none matches, pass a tight digest of the session instead.\n\n## 2. Spawn three reviewers in parallel\n\nOne message, three `subagent` calls, on the role agents below. Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, so spawn the role agents, not the built-in `explore` agent.\n\nEach reviewer and the synthesizer names a role. Spawn the agents for that role, one subagent per agent ID, from `references\u002Froles.md` in the `setup-pstack` skill. Do not pass a model. Each role agent carries its own; the operator sets them with `\u002Fpstack\u002Fsetup-pstack`.\n\n| Lens | Role | Prompt template |\n|---|---|---|\n| Judgment | `reflect judgment, divergent, synthesizer` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect tooling` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect judgment, divergent, synthesizer` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in the `subagent` response body.\n\n## 3. Synthesize\n\nOne `subagent` call on the `reflect judgment, divergent, synthesizer` role agent, from `references\u002Froles.md` in the `setup-pstack` skill. Do not pass a model. It spot-verifies citations through MCP, so spawn the role agent, not the built-in `explore` agent. Pass `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. It returns an Accepted \u002F Rejected \u002F Backlog list.\n\n## 4. Structural enforcement check\n\nMove any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n## 5. Apply\n\nPresent the synthesizer's full Accepted \u002F Rejected \u002F Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nFile each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.\n\nFollow each approved row's Routing exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the Authoring a skill playbook (`playbooks\u002Fauthoring-a-skill.md`) in the **poteto-mode** skill and run its draft \u002F test \u002F iterate loop.\n- `tune description: \u003Cskill path>` (the skill exists but didn't trigger when it should have): hand to that playbook and run its description-optimization loop.\n- `new skill via the authoring playbook: \u003Ckebab-name>`: hand creation to that playbook. Do not invent the shape ad hoc.\n\nIf your environment ships a SKILL.md validator, run it on every touched skill before declaring done.\n\n## 6. Summarize for the user\n\nShort list, no preamble:\n\n- Edits applied: `\u003Cskill path>`. What changed, one line each.\n- New skills created: `\u003Cskill path>`. One line each (rare).\n- Backlog filed to the devex tracker: `\u003Cissue title>` (`\u003Ctags>`). One line each.\n- Dropped: one line per rejected finding + reason from the synthesizer.\n","# Reflect\n\nMine the current conversation for durable learnings, then route them into skill edits.\n\nInvoke when the user says \"reflect\" or \"\u002Fpstack\u002Freflect\". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.\n\n## 1. Locate the active transcript\n\nBefore fanning out, find this conversation in the session store. `opencode session list` prints recent sessions with their IDs and working directories. Take the one whose directory matches this workspace and whose opening user prompt is this conversation's. Export it to read it. Do not list or export sessions from other projects. That crosses workspace boundaries and reads private chats from unrelated projects.\n\n```bash\nopencode session list\nopencode session export \u003CsessionID>\n```\n\nThe database behind both is `~\u002F.local\u002Fshare\u002Fopencode\u002Fopencode.db`. For each candidate, match the first user message against the conversation's opening prompt. If none matches, pass a tight digest of the session instead.\n\n## 2. Spawn three reviewers in parallel\n\nOne message, three `subagent` calls, on the role agents below. Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, so spawn the role agents, not the built-in `explore` agent.\n\nEach reviewer and the synthesizer names a role. Spawn the agents for that role, one subagent per agent ID, from `references\u002Froles.md` in the `setup-pstack` skill. Do not pass a model. Each role agent carries its own; the operator sets them with `\u002Fpstack\u002Fsetup-pstack`.\n\n| Lens | Role | Prompt template |\n|---|---|---|\n| Judgment | `reflect judgment, divergent, synthesizer` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect tooling` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect judgment, divergent, synthesizer` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in the `subagent` response body.\n\n## 3. Synthesize\n\nOne `subagent` call on the `reflect judgment, divergent, synthesizer` role agent, from `references\u002Froles.md` in the `setup-pstack` skill. Do not pass a model. It spot-verifies citations through MCP, so spawn the role agent, not the built-in `explore` agent. Pass `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. It returns an Accepted \u002F Rejected \u002F Backlog list.\n\n## 4. Structural enforcement check\n\nMove any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n## 5. Apply\n\nPresent the synthesizer's full Accepted \u002F Rejected \u002F Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nFile each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.\n\nFollow each approved row's Routing exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the Authoring a skill playbook (`playbooks\u002Fauthoring-a-skill.md`) in the **poteto-mode** skill and run its draft \u002F test \u002F iterate loop.\n- `tune description: \u003Cskill path>` (the skill exists but didn't trigger when it should have): hand to that playbook and run its description-optimization loop.\n- `new skill via the authoring playbook: \u003Ckebab-name>`: hand creation to that playbook. Do not invent the shape ad hoc.\n\nIf your environment ships a SKILL.md validator, run it on every touched skill before declaring done.\n\n## 6. Summarize for the user\n\nShort list, no preamble:\n\n- Edits applied: `\u003Cskill path>`. What changed, one line each.\n- New skills created: `\u003Cskill path>`. One line each (rare).\n- Backlog filed to the devex tracker: `\u003Cissue title>` (`\u003Ctags>`). One line each.\n- Dropped: one line per rejected finding + reason from the synthesizer.\n",{"name":5,"description":7},"main","dbb7a4935f614ebaec65ca3beb181bf74ed53431","skills\u002Fpstack\u002Freflect",0,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack","https:\u002F\u002Fgithub.com\u002Fbitgineer","2026-10-21 18:58:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add bitgineer\u002Fopencode-pstack --skill reflect",{"tool":36,"command":37},"bunx","bunx skills add bitgineer\u002Fopencode-pstack --skill reflect",{"tool":39,"command":40},"pnpm","pnpm dlx skills add bitgineer\u002Fopencode-pstack --skill reflect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fdivergent-reviewer.md","REFERENCE","参考文档",3695,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002Freferences\u002Fdivergent-reviewer.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fjudgment-reviewer.md",3134,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002Freferences\u002Fjudgment-reviewer.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fsynthesizer.md",4176,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002Freferences\u002Fsynthesizer.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ftooling-reviewer.md",4475,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Freflect\u002Freferences\u002Ftooling-reviewer.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7F8095YEQBD1R95S3CQNM7M","why","Trace why code works this way or why a design was chosen, from source control, trackers, docs, and telemetry. Use for rationale, regressions, or postmortems.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7F807MX84XR7FGZ1YTDPNPP","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7F804Y0KW517P76ZAYQ86ED","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7F800R1VV08YF0AKMNTPZ2J","technical-writing","Write or review docs, RFCs, readmes, PR descriptions, and commit messages in Diataxis structure with Google style, STE, and Global English.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7F7ZX5TJ2049PWXHB07MA7Y","teach","Explain a body of work so a person actually understands it, running how and why and weaving both into one clear explanation. Use for teach me this.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fteach\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M7F7ZSN544YPV34WWVFW332X","tdd","Use only when the user asks for TDD, a failing test, or a regression test, or when a bug has a cheap local test target; skip unclear or costly test paths.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftdd\u002FSKILL.md",[],[]]