[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDAM205GWABZY26SW4HJ97":3,"skill-same:01M7DDAM205GWABZY26SW4HJ97":44},{"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7DDAM205GWABZY26SW4HJ97","ship",null,"Commit, push and open a pull request for a completed phase, with the pipeline artifacts linked. Keywords: ship, PR, pull request, commit, push, open a PR, submit.","girishmotwani\u002Fatom","girishmotwani","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20937791?v=4","01M7DD9G6RCNXB9G6A33Z0GA1P","01M7DD9G7VT0Z0JHV97PSR0GN9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ship\ndescription: 'Commit, push and open a pull request for a completed phase, with the pipeline artifacts linked. Keywords: ship, PR, pull request, commit, push, open a PR, submit.'\n---\n\n# \u002Fatom:ship\n\nGets a completed phase into review on GitHub.\n\n## When to use\n\n- A phase passed `\u002Fatom:tdd` and `\u002Fatom:review` and was approved\n\n## Before you start\n\n`atom check` must be green **right now**. Not \"green when I last ran it\" — re-run it.\n\n---\n\n## Step 1 — Review your own diff\n\nRead the whole diff before committing. You are looking for what shouldn't be there:\n\n- Debug prints, commented-out code, stray `TODO`s you added\n- Files you didn't mean to touch\n- Anything under `.atom\u002F` that should be ignored\n- Credentials, tokens, hostnames, real customer data\n\n> **Never commit a secret.** If one has already been committed locally, stop and tell\n> the developer — do not push and do not quietly amend it away, because the object\n> still exists in the local history and needs deliberate removal.\n\n## Step 2 — Commit\n\nOne phase, one commit, unless the developer wants otherwise.\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cwhat changed>\n\n\u003Cwhy it changed, and what it enables>\n\nPhase: NN-\u003Cslug>\nSpec:  specs\u002F\u003Cproject>\u002Fphase-NN-\u003Cslug>\u002Fdesign-spec.md\nPOC:   specs\u002F\u003Cproject>\u002Fphase-NN-\u003Cslug>\u002Fpoc-report.md\n```\n\nTypes: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`.\n\nThe body explains **why**. The diff already shows what.\n\nCommit `specs\u002F` and `poc\u002F` alongside the code. They are the record of how the design\nwas arrived at, and they are worth more attached to the commit that used them than\nsitting in a wiki.\n\n## Step 3 — Push\n\n> **Do not push unless the developer has asked you to.**\n\nCommitting locally is always fine. Pushing is a visible, shared action — it needs an\nexplicit instruction, not an inferred one. \"Finish the phase\" is not \"push it\".\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\n## Step 4 — Open the pull request\n\n```bash\natom ship --pr\n```\n\nThe description is assembled from the artifacts you already wrote:\n\n```markdown\n## What\n{phase objective from the phase plan}\n\n## Why\n{purpose from the design spec}\n\n## Evidence\nPOC verdict: {Confirmed}  →  specs\u002F...\u002Fpoc-report.md\n{verbatim key output from the POC}\n\n## Verification\n{verbatim atom check output}\n\n## Review\n{n} models, {n} blockers resolved  →  specs\u002F...\u002Freview.md\n\n## Artifacts\n- Design spec: ...\n- Test spec:   ...\n- Findings:    ...\n- Decisions:   ...\n\n## Notes for the reviewer\n{anything genuinely uncertain, and what you deliberately did not do}\n```\n\nThat last section is the one reviewers actually use. Fill it honestly — flagging your\nown weak spot costs a sentence and saves a review round trip.\n\n## Step 5 — Report\n\nGive the developer the PR URL, what's in it, and what's still open in `findings.md`.\n\n---\n\n## Done when\n\n- [ ] `atom check` green, re-run immediately before committing\n- [ ] Diff read end to end; no debris, no secrets\n- [ ] Commit message explains why, and links spec and POC report\n- [ ] `specs\u002F` and `poc\u002F` committed with the code\n- [ ] Pushed **only** after an explicit instruction to push\n- [ ] PR description carries real evidence, not claims\n- [ ] Open findings surfaced to the developer\n\n## Next\n\nThe next phase's `\u002Fatom:poc` — or done, if that was the last phase.\n","# \u002Fatom:ship\n\nGets a completed phase into review on GitHub.\n\n## When to use\n\n- A phase passed `\u002Fatom:tdd` and `\u002Fatom:review` and was approved\n\n## Before you start\n\n`atom check` must be green **right now**. Not \"green when I last ran it\" — re-run it.\n\n---\n\n## Step 1 — Review your own diff\n\nRead the whole diff before committing. You are looking for what shouldn't be there:\n\n- Debug prints, commented-out code, stray `TODO`s you added\n- Files you didn't mean to touch\n- Anything under `.atom\u002F` that should be ignored\n- Credentials, tokens, hostnames, real customer data\n\n> **Never commit a secret.** If one has already been committed locally, stop and tell\n> the developer — do not push and do not quietly amend it away, because the object\n> still exists in the local history and needs deliberate removal.\n\n## Step 2 — Commit\n\nOne phase, one commit, unless the developer wants otherwise.\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cwhat changed>\n\n\u003Cwhy it changed, and what it enables>\n\nPhase: NN-\u003Cslug>\nSpec:  specs\u002F\u003Cproject>\u002Fphase-NN-\u003Cslug>\u002Fdesign-spec.md\nPOC:   specs\u002F\u003Cproject>\u002Fphase-NN-\u003Cslug>\u002Fpoc-report.md\n```\n\nTypes: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`.\n\nThe body explains **why**. The diff already shows what.\n\nCommit `specs\u002F` and `poc\u002F` alongside the code. They are the record of how the design\nwas arrived at, and they are worth more attached to the commit that used them than\nsitting in a wiki.\n\n## Step 3 — Push\n\n> **Do not push unless the developer has asked you to.**\n\nCommitting locally is always fine. Pushing is a visible, shared action — it needs an\nexplicit instruction, not an inferred one. \"Finish the phase\" is not \"push it\".\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\n## Step 4 — Open the pull request\n\n```bash\natom ship --pr\n```\n\nThe description is assembled from the artifacts you already wrote:\n\n```markdown\n## What\n{phase objective from the phase plan}\n\n## Why\n{purpose from the design spec}\n\n## Evidence\nPOC verdict: {Confirmed}  →  specs\u002F...\u002Fpoc-report.md\n{verbatim key output from the POC}\n\n## Verification\n{verbatim atom check output}\n\n## Review\n{n} models, {n} blockers resolved  →  specs\u002F...\u002Freview.md\n\n## Artifacts\n- Design spec: ...\n- Test spec:   ...\n- Findings:    ...\n- Decisions:   ...\n\n## Notes for the reviewer\n{anything genuinely uncertain, and what you deliberately did not do}\n```\n\nThat last section is the one reviewers actually use. Fill it honestly — flagging your\nown weak spot costs a sentence and saves a review round trip.\n\n## Step 5 — Report\n\nGive the developer the PR URL, what's in it, and what's still open in `findings.md`.\n\n---\n\n## Done when\n\n- [ ] `atom check` green, re-run immediately before committing\n- [ ] Diff read end to end; no debris, no secrets\n- [ ] Commit message explains why, and links spec and POC report\n- [ ] `specs\u002F` and `poc\u002F` committed with the code\n- [ ] Pushed **only** after an explicit instruction to push\n- [ ] PR description carries real evidence, not claims\n- [ ] Open findings surfaced to the developer\n\n## Next\n\nThe next phase's `\u002Fatom:poc` — or done, if that was the last phase.\n",{"name":5,"description":7},"main","5bb33cbe2c835382b5ccda840c5268321b24ac0b","skills\u002Fship","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom","https:\u002F\u002Fgithub.com\u002Fgirishmotwani","curious about all things distributed ","2026-11-13 16:16:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add girishmotwani\u002Fatom --skill ship",{"tool":36,"command":37},"bunx","bunx skills add girishmotwani\u002Fatom --skill ship",{"tool":39,"command":40},"pnpm","pnpm dlx skills add girishmotwani\u002Fatom --skill ship","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",true,[],[45,52,59,64,71,78],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DDBYEX4YKKBSQQP3HEGJC1","tdd","Implement one phase test-first in Go: red, green, refactor, against an approved design spec. Keywords: TDD, test driven, test first, implement, red green refactor, build the phase, write the code.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7DDBT5MMFRRBZJQ01VHNDGK","spec","Write the high-level design spec for one phase, grounded in that phase POC evidence. Keywords: spec, design, design doc, architecture, API design, describe the approach.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":60,"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":61,"categories":62,"keywords":63,"publishedAt":18},"01M7DDBQ3NXQKG74B1RCHDKK9T","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7DDBJMHEDT9VPGR1GJZD8CN","review","Standalone or phase multi-model review of a Go diff, merged into one report with severities. Keywords: review, code review, multi-model review, review my changes, review the diff, critique.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7DDBD2G9WVYVFCTYNYFTWAE","poc","Build, run and evaluate a throwaway Go spike that answers one falsifiable question. Produces a POC Report with verbatim evidence. Keywords: POC, proof of concept, spike, prototype, prove it, experiment, try it out.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fpoc\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7DDB98QNSK2WG5MMHH7S6J4","plan","Break proven work into ordered, independently shippable phases based on POC evidence. Keywords: plan, phases, break down, roadmap, decompose, milestones, sequencing.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]