[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVKVAQH7BZST3FQE7FD7N3":3,"skill-same:01M7CVKVAQH7BZST3FQE7FD7N3":89},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CVKVAQH7BZST3FQE7FD7N3","verify-open-pstack",null,"Verify Open Pstack through installed Codex and Claude Code skills and its shipped Bun CLIs. Use for real behavior proof, routing or setup changes, orchestration bookkeeping, and release evidence.","arjitj2\u002Fopen-pstack","arjitj2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15092149?v=4","01M7CVKN74D16AA1B4Y0CP3JKA","Arjit Jaiswal","01M7CVKN7SCSQVHE6GTQZC7XN6",16,"MIT","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: verify-open-pstack\ndescription: Verify Open Pstack through installed Codex and Claude Code skills and its shipped Bun CLIs. Use for real behavior proof, routing or setup changes, orchestration bookkeeping, and release evidence.\n---\n\n# Verify Open Pstack\n\nRead [the feature map](features\u002FREADME.md) first. The primary product is the installed Pstack workflow in Codex and Claude Code. The secondary surfaces are the shipped CLI tools. A CLI proof establishes only that CLI's behavior, never installed skill discovery, parent decisions, or model execution.\n\nThis is repository maintenance tooling, outside `plugins\u002Fpstack`. Track work in GitHub Issues; this skill originated in [issue 26](https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fissues\u002F26). Read `UPSTREAM.md` before modifying upstream-derived content.\n\n## Launch\n\nRun from the Open Pstack checkout in one Bash session. There is no server, port, database seed, or build step. Bun installs the CLI dependencies; Python 3 checks observed JSON. Installation may access the package registry. Each CLI invocation exits on its own.\n\n```bash\nset -euo pipefail\nVERIFY_REPO=$(git rev-parse --show-toplevel)\nVERIFY_TOOLS=\"$VERIFY_REPO\u002Fplugins\u002Fpstack\u002Fskills\u002Fpoteto-mode\u002Fscripts\"\nVERIFY_EVIDENCE=$(mktemp -d \"$HOME\u002Fopen-pstack-verification.XXXXXX\")\nVERIFY_SCRATCH=$(mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fopen-pstack-verify.XXXXXX\")\nexport VERIFY_REPO VERIFY_TOOLS VERIFY_EVIDENCE VERIFY_SCRATCH\ncleanup() {\n  if [ -d \"$VERIFY_SCRATCH\" ]; then\n    cp -R \"$VERIFY_SCRATCH\" \"$VERIFY_EVIDENCE\u002Fscratch-final\"\n    rm -rf -- \"$VERIFY_SCRATCH\"\n  fi\n}\ntrap cleanup EXIT\ncapture() {\n  local label=$1 rc=0\n  shift\n  printf '%q ' \"$@\" > \"$VERIFY_EVIDENCE\u002F$label.command\"\n  printf '\\n' >> \"$VERIFY_EVIDENCE\u002F$label.command\"\n  \"$@\" > \"$VERIFY_EVIDENCE\u002F$label.stdout\" 2> \"$VERIFY_EVIDENCE\u002F$label.stderr\" || rc=$?\n  printf '%s\\n' \"$rc\" > \"$VERIFY_EVIDENCE\u002F$label.exit\"\n  cat \"$VERIFY_EVIDENCE\u002F$label.stdout\"\n  cat \"$VERIFY_EVIDENCE\u002F$label.stderr\" >&2\n  return \"$rc\"\n}\nprintf '%s\\n' \"$VERIFY_EVIDENCE\"\ncapture revision git rev-parse HEAD\ncapture initial-status git status --short\ncapture plugin-before git ls-files -s plugins\u002Fpstack\ncapture install bun install --frozen-lockfile --cwd \"$VERIFY_TOOLS\"\n```\n\nReadiness means install exits zero and Doctor passes. For parent-app checks, use the installation feature's separate launch instructions. Real providers require their existing authenticated subscriptions and the saved model sheet's spending policy. Do not print credentials, invent access, or run provider probes just to verify a local CLI.\n\n## Doctor\n\nThis single read-only command checks the checkout identity, matching manifest versions, installed CLI dependency, runtime, and actual CLI entry point. Run it after Launch and again if anything looks wrong. It checks CLI readiness, not parent authentication.\n\n```bash\ncapture doctor bun -e '\nconst root = process.env.VERIFY_REPO;\nconst tools = process.env.VERIFY_TOOLS;\nconst a = await Bun.file(`${root}\u002Fplugins\u002Fpstack\u002F.claude-plugin\u002Fplugin.json`).json();\nconst b = await Bun.file(`${root}\u002Fplugins\u002Fpstack\u002F.codex-plugin\u002Fplugin.json`).json();\nif (a.name !== \"pstack\" || b.name !== \"pstack\" || a.version !== b.version) throw Error(\"manifest mismatch\");\nif (!await Bun.file(`${tools}\u002Fnode_modules\u002Fcommander\u002Fpackage.json`).exists()) throw Error(\"run Launch first\");\nconst p = Bun.spawnSync([process.execPath, `${tools}\u002Forch\u002Forch.ts`, \"--help\"]);\nif (p.exitCode !== 0 || !p.stdout.toString().includes(\"Plain-file orchestrate bookkeeping\")) throw Error(\"CLI unavailable\");\nconsole.log(JSON.stringify({root, version:a.version, bun:Bun.version, surface:\"checkout CLI\"}));'\n```\n\n## Drive\n\nChoose the changed feature, then execute its recipe with the variables and `capture` function above. Start with [orchestration](features\u002Forchestration.md) for a self-contained live CLI smoke. Use fresh scratch and evidence directories for every attempt; never use the user's default orchestrate store. Separate CLI stores can run concurrently, but dependency installation should finish before any CLI drive begins.\n\nParent installations, authentication, and model sheets are shared state unless a dedicated test profile is provided. Do not double-drive a parent session or change a personal model sheet for a fixture. When no isolated authenticated parent is available, record that entry point as blocked; continue independent CLI coverage.\n\n## Evidence\n\n`$VERIFY_EVIDENCE` is a persistent directory under the user's home, separate from disposable scratch. Every command produces `.command`, `.stdout`, `.stderr`, and `.exit` files. Use unique capture labels. Preserve fixture bytes, before\u002Fafter model sheets without secrets, runner receipts, native host events, and parent transcripts or screenshots as applicable.\n\nRecord feature ID, entry point, checkout commit and dirty diff, installed version and candidate-tree identity for parent runs, action, expected result, observed result, and skips in `result.md` in that directory. Capture the action and resulting state. Confirm writes through a second CLI read and stored files; final agent prose alone is not proof. Never fabricate provider failures or count synthetic policy inputs as a real fallback execution. Mocks belong only at an existing production boundary and must be labeled. Do not assume a dry-run is offline or side-effect-free: observe files, git refs, and network activity for the behavior being claimed.\n\nBefore release, install the exact candidate and exercise changed behavior in **every affected parent**. Unit tests, source checks, CLI policy decisions, and model self-reports cannot replace this gate. Follow `.github\u002Fpull_request_template.md`; missing applicable live evidence means draft. For maintenance-only changes, prove `plugins\u002Fpstack` unchanged and exercise the actual changed maintenance path instead.\n\n## Cleanup\n\nRun even after a failed drive. The EXIT trap covers failures in the Bash session; explicitly run the following on success. The copied scratch state survives for inspection. Keep the evidence directory.\n\n```bash\ncapture plugin-after git ls-files -s plugins\u002Fpstack\ncapture plugin-index-equality diff -u \"$VERIFY_EVIDENCE\u002Fplugin-before.stdout\" \"$VERIFY_EVIDENCE\u002Fplugin-after.stdout\"\ncapture plugin-working-tree git diff --exit-code HEAD -- plugins\u002Fpstack\ncapture plugin-untracked git ls-files --others --exclude-standard -- plugins\u002Fpstack\ntest ! -s \"$VERIFY_EVIDENCE\u002Fplugin-untracked.stdout\"\ncleanup\ntest ! -e \"$VERIFY_SCRATCH\"\ntest -s \"$VERIFY_EVIDENCE\u002Fdoctor.stdout\"\nprintf 'Scratch removed; evidence retained at %s\\n' \"$VERIFY_EVIDENCE\"\ntrap - EXIT\n```\n\nTree-equality checks above apply to maintenance-only work and should fail if packaged files changed. For intentional plugin changes, retain the diff and use installed-candidate proof instead. Close only parent sessions created for this run and remove only their dedicated test profiles. Never kill by process name or delete shared plugin caches. Foreground CLI checks here leave no background process.\n\n## Helpers\n\nNo helper executable is shipped. Launch defines the shell functions used throughout. The product executables are `bun \"$VERIFY_TOOLS\u002Forch\u002Forch.ts\"`, `\"$VERIFY_TOOLS\u002Fmodel-policy\u002Fpstack-model-policy\"`, and `\"$VERIFY_TOOLS\u002Frunner\u002Fpstack-runner\"`; use the feature recipes for arguments.\n\nKeep this map current with `pstack:maintain-verification-skill` (`\u002Fpstack:maintain-verification-skill` in Claude Code).\n","# Verify Open Pstack\n\nRead [the feature map](features\u002FREADME.md) first. The primary product is the installed Pstack workflow in Codex and Claude Code. The secondary surfaces are the shipped CLI tools. A CLI proof establishes only that CLI's behavior, never installed skill discovery, parent decisions, or model execution.\n\nThis is repository maintenance tooling, outside `plugins\u002Fpstack`. Track work in GitHub Issues; this skill originated in [issue 26](https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fissues\u002F26). Read `UPSTREAM.md` before modifying upstream-derived content.\n\n## Launch\n\nRun from the Open Pstack checkout in one Bash session. There is no server, port, database seed, or build step. Bun installs the CLI dependencies; Python 3 checks observed JSON. Installation may access the package registry. Each CLI invocation exits on its own.\n\n```bash\nset -euo pipefail\nVERIFY_REPO=$(git rev-parse --show-toplevel)\nVERIFY_TOOLS=\"$VERIFY_REPO\u002Fplugins\u002Fpstack\u002Fskills\u002Fpoteto-mode\u002Fscripts\"\nVERIFY_EVIDENCE=$(mktemp -d \"$HOME\u002Fopen-pstack-verification.XXXXXX\")\nVERIFY_SCRATCH=$(mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fopen-pstack-verify.XXXXXX\")\nexport VERIFY_REPO VERIFY_TOOLS VERIFY_EVIDENCE VERIFY_SCRATCH\ncleanup() {\n  if [ -d \"$VERIFY_SCRATCH\" ]; then\n    cp -R \"$VERIFY_SCRATCH\" \"$VERIFY_EVIDENCE\u002Fscratch-final\"\n    rm -rf -- \"$VERIFY_SCRATCH\"\n  fi\n}\ntrap cleanup EXIT\ncapture() {\n  local label=$1 rc=0\n  shift\n  printf '%q ' \"$@\" > \"$VERIFY_EVIDENCE\u002F$label.command\"\n  printf '\\n' >> \"$VERIFY_EVIDENCE\u002F$label.command\"\n  \"$@\" > \"$VERIFY_EVIDENCE\u002F$label.stdout\" 2> \"$VERIFY_EVIDENCE\u002F$label.stderr\" || rc=$?\n  printf '%s\\n' \"$rc\" > \"$VERIFY_EVIDENCE\u002F$label.exit\"\n  cat \"$VERIFY_EVIDENCE\u002F$label.stdout\"\n  cat \"$VERIFY_EVIDENCE\u002F$label.stderr\" >&2\n  return \"$rc\"\n}\nprintf '%s\\n' \"$VERIFY_EVIDENCE\"\ncapture revision git rev-parse HEAD\ncapture initial-status git status --short\ncapture plugin-before git ls-files -s plugins\u002Fpstack\ncapture install bun install --frozen-lockfile --cwd \"$VERIFY_TOOLS\"\n```\n\nReadiness means install exits zero and Doctor passes. For parent-app checks, use the installation feature's separate launch instructions. Real providers require their existing authenticated subscriptions and the saved model sheet's spending policy. Do not print credentials, invent access, or run provider probes just to verify a local CLI.\n\n## Doctor\n\nThis single read-only command checks the checkout identity, matching manifest versions, installed CLI dependency, runtime, and actual CLI entry point. Run it after Launch and again if anything looks wrong. It checks CLI readiness, not parent authentication.\n\n```bash\ncapture doctor bun -e '\nconst root = process.env.VERIFY_REPO;\nconst tools = process.env.VERIFY_TOOLS;\nconst a = await Bun.file(`${root}\u002Fplugins\u002Fpstack\u002F.claude-plugin\u002Fplugin.json`).json();\nconst b = await Bun.file(`${root}\u002Fplugins\u002Fpstack\u002F.codex-plugin\u002Fplugin.json`).json();\nif (a.name !== \"pstack\" || b.name !== \"pstack\" || a.version !== b.version) throw Error(\"manifest mismatch\");\nif (!await Bun.file(`${tools}\u002Fnode_modules\u002Fcommander\u002Fpackage.json`).exists()) throw Error(\"run Launch first\");\nconst p = Bun.spawnSync([process.execPath, `${tools}\u002Forch\u002Forch.ts`, \"--help\"]);\nif (p.exitCode !== 0 || !p.stdout.toString().includes(\"Plain-file orchestrate bookkeeping\")) throw Error(\"CLI unavailable\");\nconsole.log(JSON.stringify({root, version:a.version, bun:Bun.version, surface:\"checkout CLI\"}));'\n```\n\n## Drive\n\nChoose the changed feature, then execute its recipe with the variables and `capture` function above. Start with [orchestration](features\u002Forchestration.md) for a self-contained live CLI smoke. Use fresh scratch and evidence directories for every attempt; never use the user's default orchestrate store. Separate CLI stores can run concurrently, but dependency installation should finish before any CLI drive begins.\n\nParent installations, authentication, and model sheets are shared state unless a dedicated test profile is provided. Do not double-drive a parent session or change a personal model sheet for a fixture. When no isolated authenticated parent is available, record that entry point as blocked; continue independent CLI coverage.\n\n## Evidence\n\n`$VERIFY_EVIDENCE` is a persistent directory under the user's home, separate from disposable scratch. Every command produces `.command`, `.stdout`, `.stderr`, and `.exit` files. Use unique capture labels. Preserve fixture bytes, before\u002Fafter model sheets without secrets, runner receipts, native host events, and parent transcripts or screenshots as applicable.\n\nRecord feature ID, entry point, checkout commit and dirty diff, installed version and candidate-tree identity for parent runs, action, expected result, observed result, and skips in `result.md` in that directory. Capture the action and resulting state. Confirm writes through a second CLI read and stored files; final agent prose alone is not proof. Never fabricate provider failures or count synthetic policy inputs as a real fallback execution. Mocks belong only at an existing production boundary and must be labeled. Do not assume a dry-run is offline or side-effect-free: observe files, git refs, and network activity for the behavior being claimed.\n\nBefore release, install the exact candidate and exercise changed behavior in **every affected parent**. Unit tests, source checks, CLI policy decisions, and model self-reports cannot replace this gate. Follow `.github\u002Fpull_request_template.md`; missing applicable live evidence means draft. For maintenance-only changes, prove `plugins\u002Fpstack` unchanged and exercise the actual changed maintenance path instead.\n\n## Cleanup\n\nRun even after a failed drive. The EXIT trap covers failures in the Bash session; explicitly run the following on success. The copied scratch state survives for inspection. Keep the evidence directory.\n\n```bash\ncapture plugin-after git ls-files -s plugins\u002Fpstack\ncapture plugin-index-equality diff -u \"$VERIFY_EVIDENCE\u002Fplugin-before.stdout\" \"$VERIFY_EVIDENCE\u002Fplugin-after.stdout\"\ncapture plugin-working-tree git diff --exit-code HEAD -- plugins\u002Fpstack\ncapture plugin-untracked git ls-files --others --exclude-standard -- plugins\u002Fpstack\ntest ! -s \"$VERIFY_EVIDENCE\u002Fplugin-untracked.stdout\"\ncleanup\ntest ! -e \"$VERIFY_SCRATCH\"\ntest -s \"$VERIFY_EVIDENCE\u002Fdoctor.stdout\"\nprintf 'Scratch removed; evidence retained at %s\\n' \"$VERIFY_EVIDENCE\"\ntrap - EXIT\n```\n\nTree-equality checks above apply to maintenance-only work and should fail if packaged files changed. For intentional plugin changes, retain the diff and use installed-candidate proof instead. Close only parent sessions created for this run and remove only their dedicated test profiles. Never kill by process name or delete shared plugin caches. Foreground CLI checks here leave no background process.\n\n## Helpers\n\nNo helper executable is shipped. Launch defines the shell functions used throughout. The product executables are `bun \"$VERIFY_TOOLS\u002Forch\u002Forch.ts\"`, `\"$VERIFY_TOOLS\u002Fmodel-policy\u002Fpstack-model-policy\"`, and `\"$VERIFY_TOOLS\u002Frunner\u002Fpstack-runner\"`; use the feature recipes for arguments.\n\nKeep this map current with `pstack:maintain-verification-skill` (`\u002Fpstack:maintain-verification-skill` in Claude Code).\n",{"name":5,"description":7},"main","264230bc14d9055d1333804799e7187e8e6e135c",".agents\u002Fskills\u002Fverify-open-pstack",2,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack","https:\u002F\u002Fgithub.com\u002Farjitj2","https:\u002F\u002Farjit.me\u002F","I want to work with great people to build great things that change the world.","2026-11-04 11:44:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add arjitj2\u002Fopen-pstack --skill verify-open-pstack",{"tool":39,"command":40},"bunx","bunx skills add arjitj2\u002Fopen-pstack --skill verify-open-pstack",{"tool":42,"command":43},"pnpm","pnpm dlx skills add arjitj2\u002Fopen-pstack --skill verify-open-pstack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002FSKILL.md",true,[47,53,57,61,65,69,73,77,81,85],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"features\u002Finstallation.md","REFERENCE","参考文档",2633,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Finstallation.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"features\u002Fmaintenance.md",4551,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fmaintenance.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"features\u002Forchestration.md",6135,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Forchestration.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"features\u002FREADME.md",2368,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002FREADME.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"features\u002Frouting.md",17381,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Frouting.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"features\u002Fsetup.md",3658,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fsetup.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"features\u002Fstartup-routing.md",4770,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fstartup-routing.md",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"features\u002Fworker-contract.md",12762,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fworker-contract.md",{"path":82,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":83,"sourceHtmlUrl":84},"features\u002Fworker-progress.md",6408,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fworker-progress.md",{"path":86,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":87,"sourceHtmlUrl":88},"features\u002Fworkflows.md",39122,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-open-pstack\u002Ffeatures\u002Fworkflows.md",[90,97,104,111,118,125],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CVW5H20VXPF7Z01VXY20G2","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CVW3937916EAX061GZTS4A","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7CVW0Z4XXRTZ4GGCW4CT95B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7CVVXMMWBB13598A412BXPR","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7CVVSD76JCSPTD6P55K24B0","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7CVVN2PRJKWMSXTH2G6SBWY","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]