[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C71E9TSHBHF07KENPH4BJR":3,"skill-same:01M7C71E9TSHBHF07KENPH4BJR":47},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7C71E9TSHBHF07KENPH4BJR","commit",null,"Create small, atomic, Conventional Commits. Use when the user asks to commit, split work into commits, draft commit messages, or stage related changes — never for drive-by mega-commits.","OctavianTocan\u002Fagentic-inbox","OctavianTocan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55554752?v=4","01M7C71C9259P2V7FB54046SB4","Octavian Tocan","01M7C71C9VKZRJWXZNZG1BA4PH",0,"MIT","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commit\ndescription: \"Create small, atomic, Conventional Commits. Use when the user asks to commit, split work into commits, draft commit messages, or stage related changes — never for drive-by mega-commits.\"\n---\n\n# Commit\n\nTeach the agent to land work as **small**, **atomic**, **Conventional Commits** that match this repo’s history.\n\n## What This Skill Does\n\n1. Land the **entire** dirty tree — every tracked change and every intentional untracked file\n2. Split that tree into one-logical-change commits\n3. Write Conventional Commit subjects focused on **why**\n4. Stage only the files that belong to each change (narrow staging, full coverage)\n5. Follow git safety rules (no secrets, no force, no surprise amends)\n\n## When to use\n\n- User says commit \u002F commit this \u002F split into commits \u002F push with commits\n- You finished a coherent slice and they asked you to land it\n- A working tree mixes unrelated concerns (schema + rules + feature) that should not share one SHA\n\n**Do not** invent commits the user did not ask for.\n\n---\n\n## Quick Start\n\n1. Inspect in parallel: `git status`, `git diff` (+ `--cached`), `git log -8 --oneline`\n2. Group **all** dirty files into atomic buckets (one concern each) — nothing left over\n3. For each bucket: stage → commit with HEREDOC → next bucket\n4. `git status` after the last commit must be clean (only secrets\u002Fignored noise may remain, and those need a warning)\n\nMessage shape (match recent log: `feat(db):`, `docs(wayfinder):`, `fix(triage):`):\n\n```text\ntype(optional-scope): imperative summary ≤ ~72 chars\n\nOptional body: why, not a file list.\n```\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfeat(triage): add runs repo with whole-entity upsert\n\nPersist triage attempts as upsertable aggregates so services own status transitions.\n\nEOF\n)\"\n```\n\n---\n\n## Atomicity rules\n\nOne commit = one restore point a reviewer can reason about.\n\n| Do | Don’t |\n|----|--------|\n| Schema migration alone | Migration + UI + evals in one commit |\n| OCR\u002Fskill rule updates alone | Rules bundled with unrelated feature code |\n| One module’s repo + its import renames | “Phase 1 WIP” kitchen sink |\n| Test fixes required by that API change | Unrelated test flakiness |\n\n**Split when** the message would need “and” between unrelated nouns (“add runs table and rename chat components”).\n\n**Keep together when** the change is one behavior and tests\u002Ftypes must move with it to stay green (e.g. new required field + call-site defaults).\n\nPrefer **2–5 focused commits** over one large commit when the tree clearly has layers (docs → schema → domain → wiring).\n\n---\n\n## Conventional Commits (this repo)\n\n**Types** (common here): `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `ci`.\n\n**Scopes** (optional, lowercase): area nouns from the change — `db`, `triage`, `actions`, `api-core`, `wayfinder`, `web`, `ocr`, …\n\n**Subject**:\n- Imperative mood: “add”, “fix”, “expand” — not “added” \u002F “adds”\n- No trailing period\n- Why-leaning: say the outcome, not every file\n\n**Body** (optional): 1–3 lines on motivation or constraint; not a `git status` dump.\n\nExamples from this lineage:\n\n```text\ndocs(wayfinder): close Must-have map with defaults and build plan\nfeat(db): expand initial schema for runs, traces, and evals\n```\n\n---\n\n## Procedure (every commit)\n\n### 1. Survey\n\nRun together:\n\n- `git status`\n- `git diff` and `git diff --cached`\n- `git log -8 --oneline` (match tone\u002Fscope style)\n\n### 2. Plan buckets\n\nList proposed commits before staging, e.g.:\n\n1. `docs(ocr): require whole-entity repos and sub-modules`\n2. `refactor(triage): nest Decisions repo under Triage\u002FDecisions`\n3. `feat(triage): add TriageRunsRepo upsert surface`\n\nAsk the user to confirm the split only if the bucketing is ambiguous; otherwise proceed when they already asked to commit.\n\nEvery path from `git status` belongs in some bucket (or is a secret \u002F truly accidental local junk you must ask about). Do not silently skip “small” or “unrelated” files.\n\n### 3. Stage narrowly\n\n```bash\ngit add path\u002Fto\u002Frelevant\u002Ffiles\n```\n\nNever `git add .` unless the entire diff is one atomic change. Unstage anything that belongs in the next commit — but those files still get committed in a later bucket in the same `\u002Fcommit` pass.\n\n### 4. Commit\n\n- HEREDOC message (see Quick Start)\n- No `--no-verify` unless the user explicitly allows skipping hooks\n- No `git commit --amend` unless all of: user requested amend **or** hook auto-modified files that must be included; HEAD was created by you in this conversation; commit not pushed\n- If a hook **rejects** the commit: fix, then make a **new** commit (do not amend the failed one)\n\n### 5. Verify\n\n`git status` — clean, or only the next planned bucket left. Repeat until the working tree is clean. Leaving random edits unstaged after `\u002Fcommit` is a failure.\n\n### 6. Push\n\nOnly if the user asked to push. Prefer `git push -u origin HEAD` on feature branches.\n\n---\n\n## Safety (hard rules)\n\n- **Never** update git config\n- **Never** commit secrets (`.env`, credentials, private keys). Warn and leave those out; still commit everything else\n- **Never** force-push `main`\u002F`master`; warn on any `--force`\n- **Never** use interactive flags (`git add -i`, `git rebase -i`)\n- **Commit all non-secret dirty paths.** Local editor tweaks (e.g. `.vscode\u002Fsettings.json`), docs, and “accidental” edits are still part of the tree — put them in their own `chore`\u002F`docs` commit or ask once if the intent is truly unclear. Do not quietly leave them unstaged.\n\n---\n\n## Hook failures\n\nPre-commit may run lint\u002Ftests\u002Ftypecheck. If it fails:\n\n1. Read the hook output\n2. Fix the underlying issue (or split out the broken concern)\n3. Create a **new** commit with the fix\n\nDo not disable hooks to “get it through.”\n\n---\n\n## Anti-patterns\n\n- `git commit -m \"wip\"` \u002F `updates` \u002F `fix stuff`\n- One commit that mixes `feat` + `docs(ocr)` + unrelated refactors\n- Staging generated secrets or local-only env files\n- Finishing `\u002Fcommit` with leftover unstaged\u002Funtracked files (except warned-about secrets)\n- Amending commits already on the remote without an explicit user request\n- Squashing away atomic history the user wanted to keep when they asked for small commits\n\n---\n\n## Related\n\n- User asked only to **explain** changes → no commit\n- User asked for a **PR** → commit first (if needed), then follow PR workflow\n- Repo skills: `domain-backend` for module layout that often lands in its own commit\n","# Commit\n\nTeach the agent to land work as **small**, **atomic**, **Conventional Commits** that match this repo’s history.\n\n## What This Skill Does\n\n1. Land the **entire** dirty tree — every tracked change and every intentional untracked file\n2. Split that tree into one-logical-change commits\n3. Write Conventional Commit subjects focused on **why**\n4. Stage only the files that belong to each change (narrow staging, full coverage)\n5. Follow git safety rules (no secrets, no force, no surprise amends)\n\n## When to use\n\n- User says commit \u002F commit this \u002F split into commits \u002F push with commits\n- You finished a coherent slice and they asked you to land it\n- A working tree mixes unrelated concerns (schema + rules + feature) that should not share one SHA\n\n**Do not** invent commits the user did not ask for.\n\n---\n\n## Quick Start\n\n1. Inspect in parallel: `git status`, `git diff` (+ `--cached`), `git log -8 --oneline`\n2. Group **all** dirty files into atomic buckets (one concern each) — nothing left over\n3. For each bucket: stage → commit with HEREDOC → next bucket\n4. `git status` after the last commit must be clean (only secrets\u002Fignored noise may remain, and those need a warning)\n\nMessage shape (match recent log: `feat(db):`, `docs(wayfinder):`, `fix(triage):`):\n\n```text\ntype(optional-scope): imperative summary ≤ ~72 chars\n\nOptional body: why, not a file list.\n```\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nfeat(triage): add runs repo with whole-entity upsert\n\nPersist triage attempts as upsertable aggregates so services own status transitions.\n\nEOF\n)\"\n```\n\n---\n\n## Atomicity rules\n\nOne commit = one restore point a reviewer can reason about.\n\n| Do | Don’t |\n|----|--------|\n| Schema migration alone | Migration + UI + evals in one commit |\n| OCR\u002Fskill rule updates alone | Rules bundled with unrelated feature code |\n| One module’s repo + its import renames | “Phase 1 WIP” kitchen sink |\n| Test fixes required by that API change | Unrelated test flakiness |\n\n**Split when** the message would need “and” between unrelated nouns (“add runs table and rename chat components”).\n\n**Keep together when** the change is one behavior and tests\u002Ftypes must move with it to stay green (e.g. new required field + call-site defaults).\n\nPrefer **2–5 focused commits** over one large commit when the tree clearly has layers (docs → schema → domain → wiring).\n\n---\n\n## Conventional Commits (this repo)\n\n**Types** (common here): `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `ci`.\n\n**Scopes** (optional, lowercase): area nouns from the change — `db`, `triage`, `actions`, `api-core`, `wayfinder`, `web`, `ocr`, …\n\n**Subject**:\n- Imperative mood: “add”, “fix”, “expand” — not “added” \u002F “adds”\n- No trailing period\n- Why-leaning: say the outcome, not every file\n\n**Body** (optional): 1–3 lines on motivation or constraint; not a `git status` dump.\n\nExamples from this lineage:\n\n```text\ndocs(wayfinder): close Must-have map with defaults and build plan\nfeat(db): expand initial schema for runs, traces, and evals\n```\n\n---\n\n## Procedure (every commit)\n\n### 1. Survey\n\nRun together:\n\n- `git status`\n- `git diff` and `git diff --cached`\n- `git log -8 --oneline` (match tone\u002Fscope style)\n\n### 2. Plan buckets\n\nList proposed commits before staging, e.g.:\n\n1. `docs(ocr): require whole-entity repos and sub-modules`\n2. `refactor(triage): nest Decisions repo under Triage\u002FDecisions`\n3. `feat(triage): add TriageRunsRepo upsert surface`\n\nAsk the user to confirm the split only if the bucketing is ambiguous; otherwise proceed when they already asked to commit.\n\nEvery path from `git status` belongs in some bucket (or is a secret \u002F truly accidental local junk you must ask about). Do not silently skip “small” or “unrelated” files.\n\n### 3. Stage narrowly\n\n```bash\ngit add path\u002Fto\u002Frelevant\u002Ffiles\n```\n\nNever `git add .` unless the entire diff is one atomic change. Unstage anything that belongs in the next commit — but those files still get committed in a later bucket in the same `\u002Fcommit` pass.\n\n### 4. Commit\n\n- HEREDOC message (see Quick Start)\n- No `--no-verify` unless the user explicitly allows skipping hooks\n- No `git commit --amend` unless all of: user requested amend **or** hook auto-modified files that must be included; HEAD was created by you in this conversation; commit not pushed\n- If a hook **rejects** the commit: fix, then make a **new** commit (do not amend the failed one)\n\n### 5. Verify\n\n`git status` — clean, or only the next planned bucket left. Repeat until the working tree is clean. Leaving random edits unstaged after `\u002Fcommit` is a failure.\n\n### 6. Push\n\nOnly if the user asked to push. Prefer `git push -u origin HEAD` on feature branches.\n\n---\n\n## Safety (hard rules)\n\n- **Never** update git config\n- **Never** commit secrets (`.env`, credentials, private keys). Warn and leave those out; still commit everything else\n- **Never** force-push `main`\u002F`master`; warn on any `--force`\n- **Never** use interactive flags (`git add -i`, `git rebase -i`)\n- **Commit all non-secret dirty paths.** Local editor tweaks (e.g. `.vscode\u002Fsettings.json`), docs, and “accidental” edits are still part of the tree — put them in their own `chore`\u002F`docs` commit or ask once if the intent is truly unclear. Do not quietly leave them unstaged.\n\n---\n\n## Hook failures\n\nPre-commit may run lint\u002Ftests\u002Ftypecheck. If it fails:\n\n1. Read the hook output\n2. Fix the underlying issue (or split out the broken concern)\n3. Create a **new** commit with the fix\n\nDo not disable hooks to “get it through.”\n\n---\n\n## Anti-patterns\n\n- `git commit -m \"wip\"` \u002F `updates` \u002F `fix stuff`\n- One commit that mixes `feat` + `docs(ocr)` + unrelated refactors\n- Staging generated secrets or local-only env files\n- Finishing `\u002Fcommit` with leftover unstaged\u002Funtracked files (except warned-about secrets)\n- Amending commits already on the remote without an explicit user request\n- Squashing away atomic history the user wanted to keep when they asked for small commits\n\n---\n\n## Related\n\n- User asked only to **explain** changes → no commit\n- User asked for a **PR** → commit first (if needed), then follow PR workflow\n- Repo skills: `domain-backend` for module layout that often lands in its own commit\n",{"name":5,"description":7},"main","516fd82c2b9f9a7877cd8fc3716ce85ad5aea154",".agent\u002Fskills\u002Fcommit","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox","https:\u002F\u002Fagentic-inbox.octaviantocan.com","https:\u002F\u002Fgithub.com\u002FOctavianTocan","https:\u002F\u002Foctaviantocan.com","Product & Design Engineer. React, TypeScript, React Native. Shipped at Ojin, TwinMind and a YC startup. Zaragoza, Spain.","2026-11-10 20:03:26",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add OctavianTocan\u002Fagentic-inbox --skill commit",{"tool":39,"command":40},"bunx","bunx skills add OctavianTocan\u002Fagentic-inbox --skill commit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add OctavianTocan\u002Fagentic-inbox --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fcommit\u002FSKILL.md",true,[],[48,55,62,69,76,81],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7C72EKFAYWCHT824ZRWR5ZN","testing","Testing patterns and best practices.","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002Ftools\u002Fskill-gen\u002Fe2e-test-expected\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7C72DCKJMY89MJBYBX90MH2","coding","General coding patterns and conventions.","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002Ftools\u002Fskill-gen\u002Fe2e-test-expected\u002Fcoding\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7C729AP4GNJN3KF78VV0B6E","skill-gen","Use when adding, modifying, generating, checking, or debugging repo-local skill fragments embedded in source code with \u002F\u002F\u003Cskill-gen> markers.","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002Ftools\u002Fskill-gen\u002F.agent\u002Fskills\u002Fskill-gen\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7C724TJ8XH6QKZNJP6EJSGF","gen-github-workflow","Use when creating, modifying, generating, checking, or debugging CI workflow fragments embedded in source code with \u002F\u002F\u003Cgen-github-workflow> markers.","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002Ftools\u002Fgen-github-workflow\u002F.agent\u002Fskills\u002Fgen-github-workflow\u002FSKILL.md",[],[],{"skillNo":77,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7C720VEJCXABMYNSHDS9X0C","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskill-gen\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7C71V6NRZZ43RH1KDJ3MGBD","inbox-agents-md","Decides when to create or update nested AGENTS.md, README.md, and CLAUDE.md files in the agentic-inbox monorepo. Use when adding packages\u002Fapps\u002Ftools, restructuring subtrees, writing agent docs, or when nested subtree docs may be stale or missing.","https:\u002F\u002Fgithub.com\u002FOctavianTocan\u002Fagentic-inbox\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Finbox-agents-md\u002FSKILL.md",[],[]]