[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7921B83PSB0EXHPRRJH6CF2":3,"skill-same:01M7921B83PSB0EXHPRRJH6CF2":48},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7921B83PSB0EXHPRRJH6CF2","commit",null,"Commit local changes — inspect the working tree, group into atomic conventional commits, and write messages that match the repo's conventions. Two modes: full (default, careful) and asap (fast). Use when the user has uncommitted changes, asks to commit, or invokes \u002Fcommit, \u002Fcommit full, or \u002Fcommit asap.","dotlas\u002Fskills","dotlas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F88832003?v=4","01M791ZCS9BAQ40PZ8ADG8TCR1","Dotlas","01M791ZCT18PGXY969S8EZ1MVV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcoding\u002Fcommit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commit\ndescription: \"Commit local changes — inspect the working tree, group into atomic conventional commits, and write messages that match the repo's conventions. Two modes: full (default, careful) and asap (fast). Use when the user has uncommitted changes, asks to commit, or invokes \u002Fcommit, \u002Fcommit full, or \u002Fcommit asap.\"\n---\n# Commit\n\nCommit the local changes: review the working tree, group them into atomic commits, and\ncommit. Runs in one of two modes — **`full`** (default) or **`asap`** — sharing one\nprocess and differing only in how much they slow down for proposals, hooks, and docs.\nThe [Modes](#modes) table at the end is the at-a-glance summary; the sections below\ndefine the process it summarizes.\n\n## Process\n\n1. Inspect staged and unstaged changes (`git status`, `git diff`, `git diff --cached`).\n2. Check the change set against plans (see [Plans](#plans)).\n3. Group files into one logical change per commit.\n4. Order commits so prerequisites land before dependents: dependency and config changes\n   (manifests, lockfiles, tooling) before code that relies on them; shared code before\n   its consumers; tests alongside the code they cover.\n5. Stage files by name and commit, handling any failing pre-commit hook per the active\n   mode (see [Rules](#rules)). In `full`, present the plan first when the grouping is\n   non-trivial; `asap` commits directly without proposing.\n6. In `full` only, update in-situ subdir documentation where it applies (see\n   [Subdir documentation](#subdir-documentation)). `asap` skips this.\n\n## Plans\n\nBefore committing, check whether the current change set completes or supersedes any plan\nin the repo — tracked **or** untracked.\nPlans live in no fixed place or format: a `.plans\u002F` directory, an `agent_plans\u002F` folder,\na top-level `PLAN.md`, or any variant.\n\n- If it does, ask the user with `AskUserQuestion` whether to resolve or delete that\n  plan.\n- Commit the plan’s final state before deleting it, so it survives in git history; then\n  delete it in a later commit if the user chose deletion.\n- If no plan matches, proceed silently — do not prompt.\n\nThis runs in **both** modes.\n\n## Message format\n\n```text\ntype(scope): description\n\n[body]\n\n[footer]\n```\n\n**Subject** — `type(scope): description`. Common types: `feat`, `fix`, `refactor`,\n`perf`, `docs`, `test`, `build`, `chore`, `style`, `ci`, `revert`, `ai`. `ai` is for\nagent and AI-tool config — `.agents\u002F`, `CLAUDE.md`, `.cursorrules`,\n`.github\u002Fcopilot-instructions.md`.\n\n**Body — required, in both modes, whenever the commit is a breaking change, a security\nfix, a data migration, or a revert of a prior commit.** These must never be\nsubject-only: a future debugger needs the why and the blast radius.\nElsewhere a body is optional — add one when the change isn’t self-evident from the diff.\n\n**Footer** — for breaking changes and references.\nMark a breaking change either as `type!: description` (a `!` before the colon) or with a\n`BREAKING CHANGE: \u003Cdetail>` footer; for a serious break, use both.\n\n## Conventions\n\n- Keep the description lowercase, imperative, and short.\n- Refer to the existing git log for scope conventions.\n- Use backticks for scope paths, code symbols, and new source files in the description.\n\n## Subdir documentation\n\n`full` mode only; `asap` skips it entirely.\n\nAfter the code commits, update the documentation that lives with the changed code — a\nsubdirectory’s README, knowledge file, or equivalent — when it records behaviour these\nchanges alter. Both conditions must hold, or skip:\n\n- The repo already has a documentation convention defined at a top level or agent level\n  (e.g. a docs policy, or `CLAUDE.md` \u002F `.agents\u002F` guidance describing how subdir docs\n  work).\n- The changed subdirectory itself has a doc\u002Fknowledge\u002Freadme capturing behaviour that\n  these changes affect.\n\nWork only with what exists — never create a documentation convention where the repo has\nnone. If an update needs a design judgement that can’t be deduced from the code or the\nconversation, ask the user with `AskUserQuestion` rather than guessing.\n\n## Rules\n\n- Never use `git add .` or `git add -A` — stage files by name.\n- When a pre-commit hook fails, fix it if the fix is within the same scope of work.\n  If it can’t be fixed: `full` stops and asks via `AskUserQuestion`; `asap` bypasses\n  with `git commit -n`. Bypass is an `asap`-only exception, not a licence to skip hooks\n  in `full`.\n- In `full`, present the commit plan before executing when the grouping is non-trivial.\n  `asap` skips the proposal and commits directly.\n\n## Safety\n\n- Never run `git push` (or any variant) without explicit sign-off; never force-push.\n- Never run destructive commands that discard work — `git reset --hard`,\n  `git clean -fd`, `git checkout -- .`. To undo a commit, prefer\n  `git reset --soft HEAD~1` and explain what happened.\n\n## Modes\n\nBare `\u002Fcommit` runs **`full`**. Both modes run the same Process above and remove\ncompleted plans; they differ only here:\n\n|  | `\u002Fcommit full` (default) | `\u002Fcommit asap` |\n| --- | --- | --- |\n| **Non-trivial grouping** | Propose the plan, then commit on approval. | Commit directly, no proposal. |\n| **Failing pre-commit hook** | Fix within scope; if unfixable, stop and ask via `AskUserQuestion`. Never bypass. | Fix within scope; if unfixable, bypass with `git commit -n`. |\n| **In-situ subdir docs** | Update where a convention exists. | Skip. |\n| **Completed plans** | Remove. | Remove. |\n","# Commit\n\nCommit the local changes: review the working tree, group them into atomic commits, and\ncommit. Runs in one of two modes — **`full`** (default) or **`asap`** — sharing one\nprocess and differing only in how much they slow down for proposals, hooks, and docs.\nThe [Modes](#modes) table at the end is the at-a-glance summary; the sections below\ndefine the process it summarizes.\n\n## Process\n\n1. Inspect staged and unstaged changes (`git status`, `git diff`, `git diff --cached`).\n2. Check the change set against plans (see [Plans](#plans)).\n3. Group files into one logical change per commit.\n4. Order commits so prerequisites land before dependents: dependency and config changes\n   (manifests, lockfiles, tooling) before code that relies on them; shared code before\n   its consumers; tests alongside the code they cover.\n5. Stage files by name and commit, handling any failing pre-commit hook per the active\n   mode (see [Rules](#rules)). In `full`, present the plan first when the grouping is\n   non-trivial; `asap` commits directly without proposing.\n6. In `full` only, update in-situ subdir documentation where it applies (see\n   [Subdir documentation](#subdir-documentation)). `asap` skips this.\n\n## Plans\n\nBefore committing, check whether the current change set completes or supersedes any plan\nin the repo — tracked **or** untracked.\nPlans live in no fixed place or format: a `.plans\u002F` directory, an `agent_plans\u002F` folder,\na top-level `PLAN.md`, or any variant.\n\n- If it does, ask the user with `AskUserQuestion` whether to resolve or delete that\n  plan.\n- Commit the plan’s final state before deleting it, so it survives in git history; then\n  delete it in a later commit if the user chose deletion.\n- If no plan matches, proceed silently — do not prompt.\n\nThis runs in **both** modes.\n\n## Message format\n\n```text\ntype(scope): description\n\n[body]\n\n[footer]\n```\n\n**Subject** — `type(scope): description`. Common types: `feat`, `fix`, `refactor`,\n`perf`, `docs`, `test`, `build`, `chore`, `style`, `ci`, `revert`, `ai`. `ai` is for\nagent and AI-tool config — `.agents\u002F`, `CLAUDE.md`, `.cursorrules`,\n`.github\u002Fcopilot-instructions.md`.\n\n**Body — required, in both modes, whenever the commit is a breaking change, a security\nfix, a data migration, or a revert of a prior commit.** These must never be\nsubject-only: a future debugger needs the why and the blast radius.\nElsewhere a body is optional — add one when the change isn’t self-evident from the diff.\n\n**Footer** — for breaking changes and references.\nMark a breaking change either as `type!: description` (a `!` before the colon) or with a\n`BREAKING CHANGE: \u003Cdetail>` footer; for a serious break, use both.\n\n## Conventions\n\n- Keep the description lowercase, imperative, and short.\n- Refer to the existing git log for scope conventions.\n- Use backticks for scope paths, code symbols, and new source files in the description.\n\n## Subdir documentation\n\n`full` mode only; `asap` skips it entirely.\n\nAfter the code commits, update the documentation that lives with the changed code — a\nsubdirectory’s README, knowledge file, or equivalent — when it records behaviour these\nchanges alter. Both conditions must hold, or skip:\n\n- The repo already has a documentation convention defined at a top level or agent level\n  (e.g. a docs policy, or `CLAUDE.md` \u002F `.agents\u002F` guidance describing how subdir docs\n  work).\n- The changed subdirectory itself has a doc\u002Fknowledge\u002Freadme capturing behaviour that\n  these changes affect.\n\nWork only with what exists — never create a documentation convention where the repo has\nnone. If an update needs a design judgement that can’t be deduced from the code or the\nconversation, ask the user with `AskUserQuestion` rather than guessing.\n\n## Rules\n\n- Never use `git add .` or `git add -A` — stage files by name.\n- When a pre-commit hook fails, fix it if the fix is within the same scope of work.\n  If it can’t be fixed: `full` stops and asks via `AskUserQuestion`; `asap` bypasses\n  with `git commit -n`. Bypass is an `asap`-only exception, not a licence to skip hooks\n  in `full`.\n- In `full`, present the commit plan before executing when the grouping is non-trivial.\n  `asap` skips the proposal and commits directly.\n\n## Safety\n\n- Never run `git push` (or any variant) without explicit sign-off; never force-push.\n- Never run destructive commands that discard work — `git reset --hard`,\n  `git clean -fd`, `git checkout -- .`. To undo a commit, prefer\n  `git reset --soft HEAD~1` and explain what happened.\n\n## Modes\n\nBare `\u002Fcommit` runs **`full`**. Both modes run the same Process above and remove\ncompleted plans; they differ only here:\n\n|  | `\u002Fcommit full` (default) | `\u002Fcommit asap` |\n| --- | --- | --- |\n| **Non-trivial grouping** | Propose the plan, then commit on approval. | Commit directly, no proposal. |\n| **Failing pre-commit hook** | Fix within scope; if unfixable, stop and ask via `AskUserQuestion`. Never bypass. | Fix within scope; if unfixable, bypass with `git commit -n`. |\n| **In-situ subdir docs** | Update where a convention exists. | Skip. |\n| **Completed plans** | Remove. | Remove. |\n",{"name":5,"description":7},"main","44a7c5d185b1020f689d2129547d7470c3715e76","skills\u002Fcustom\u002Fcoding\u002Fcommit",0,"https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills","https:\u002F\u002Fwww.skills.sh\u002Fdotlas\u002Fskills","https:\u002F\u002Fgithub.com\u002Fdotlas","www.dotlas.com","A platform to help companies make better city-level decisions and improve the bottom line of their retail footprint.","2026-10-27 22:40:58",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add dotlas\u002Fskills --skill commit",{"tool":40,"command":41},"bunx","bunx skills add dotlas\u002Fskills --skill commit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dotlas\u002Fskills --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcoding\u002Fcommit\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M792400972AXPY3XESVHRFRA","where-were-we","Provide the user with a refresher of existing chat turns. Useful when the user wants to understand where we stand in the conversation.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fwhere-were-we\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7923T58GM9G9TVAZB9TGTWE","update-global-dotlas-skills","Sync the globally-installed dotlas\u002Fskills catalog and prune stale remnants. Runs the documented global install command, then detects skills that were installed from dotlas\u002Fskills but no longer exist in the catalog and removes them (with confirmation). Use when the user wants to update, refresh, or clean up their global Dotlas skills, or invokes \u002Fupdate-global-dotlas-skills.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fupdate-global-dotlas-skills\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7923KGCMXT25Y7XVC6G1ERX","unpack","Explain an unfamiliar thing plainly and from first principles, structured so the reader sees why it is true. Use when someone is trying to understand something — a dense or jargon-heavy passage, a baffling error, an unfamiliar mechanism, a codebase, or a document — asks to break something down (\"walk me through this\", \"what does this actually mean\"), or wants their intent turned into a precise instruction for another agent. Trigger on confusion or a request to understand, not on difficulty alone; technical or long content is not itself a signal.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Funpack\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7923HNVVHRKRVQ5M0P7TXZA","sum","Use when the previous response is too technical, complex, or jargon-heavy and needs a clear, plain-language explanation","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fsum\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7923CY3FR71VPKBYRHZNNVH","slack","Compose a Slack message, or digest a Slack thread into compact context. Use when the user asks to reply to a person or channel, write a Slack post, or catch up on a thread without reading the whole transcript. This skill covers how to write well for Slack — both jobs share the same standard.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fslack\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79234W72RKWYV2S38G2B0SY","plan-with-me","Collaborative, human-in-the-loop planning for something new that spans several parts and needs human judgement at each fork. A brainstorming partner that funnels — each fork opens up the real options, then narrows to a decision, surfacing caveats and breaking points, and co-authoring the plan instead of guessing alone. Fits any domain where you plan something new against existing context. Resolves one decision at a time, each with a recommendation, then emits a lightweight plan to hand off for implementation. Use when planning alone would make wrong assumptions, or the user wants to shape something new together.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fplan-with-me\u002FSKILL.md",[],[]]