[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMDFJQ5ESCMBSHX3EFA1AC":3,"skill-same:01M7EMDFJQ5ESCMBSHX3EFA1AC":67},{"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMDFJQ5ESCMBSHX3EFA1AC","issue-tracking",null,"Use when agents create, select, update, comment on, close, or sync ditz issues, especially across worktrees or after uncertain or partial command results. Establish the intended tracker and use the existing CLI safely. Also use when a repo's beads\u002Fditz instructions conflict; resolve the tracker before writing. Does not initialize trackers or migrate beads.","tedks\u002Fagent-skills","tedks","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1703535?v=4","01M7EMCJYBNAVD6EN62JAPCK0X","Ted Smith","01M7EMCJYZVVBFQTGZX8W2BXVT",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: issue-tracking\ndescription: Use when agents create, select, update, comment on, close, or sync ditz issues, especially across worktrees or after uncertain or partial command results. Establish the intended tracker and use the existing CLI safely. Also use when a repo's beads\u002Fditz instructions conflict; resolve the tracker before writing. Does not initialize trackers or migrate beads.\n---\n\n# Issue tracking\n\nMake the requested issue change and report what actually happened. Repository\ninstructions govern the tracker; this skill is a small workflow around the\nexisting CLI, not a new API or a replacement for project policy.\n\n## Establish the target once per context\n\nBefore mutation, identify the intended project\u002Fworktree, executable, and store:\n\n1. Check `pwd`, repository instructions, and `git rev-parse --show-toplevel`\n   (or `git worktree list` from a bare project root). Use the assigned worktree.\n2. Resolve `command -v ditz` and read `ditz --help=plain` plus the relevant\n   subcommand's help. Respect Nix\u002FBazel project tooling rules. Prefer the\n   installed executable; if absent, report it and use an explicit project-\n   approved install or `nix run github:tedks\u002Fditz -- \u003Ccmd>` fallback. Do not\n   silently switch binaries after a failure.\n3. Inspect relevant `~\u002F.ditz-config` settings and the project's documented\n   storage mode. An existing `ditz-metadata` branch takes precedence over\n   the configured issue directory; without that branch, the configured\n   directory selects the filesystem store. Correlate a known issue or project\n   identity with that store before writing. Keep private config contents out\n   of reports.\n\nIf repo instructions, config, or the observed store disagree, resolve that\nspecific mismatch before mutation. A missing binary, failed read, or empty\nlisting is not permission to run `init`, migrate beads, create a fallback\ntracker, or declare that no issues exist. Do not apply ditz commands to a\nbeads project; use its established workflow. Recheck context after changing\nproject, executable, or config; don't repeat the full preflight per issue.\n\n## Use the current command contract\n\nRead the relevant sections of the canonical\n[agent recipes](https:\u002F\u002Fgithub.com\u002Ftedks\u002Fditz\u002Fblob\u002Fmaster\u002Fdocs\u002Fagent-recipes.md)\nand [JSON\u002Fretry contract](https:\u002F\u002Fgithub.com\u002Ftedks\u002Fditz\u002Fblob\u002Fmaster\u002Fdocs\u002Fjson-contracts.md).\nPrefer their local copies in a ditz checkout when available; compare with\ninstalled command help because that binary may predate the docs. Do not invent\nflags or a common JSON envelope across commands.\n\n- Capture IDs directly with `add --ids-only`, and retain the exact ID.\n  `add --id NAME` creates once; an existing ID returns unchanged, even if new\n  creation fields differ. Inspect it before relying on its contents; use `set`\n  for an authorized update. This is not an upsert.\n- Feed multiline descriptions\u002Fcomments through the documented stdin flags\n  using a quoted here-document or owned file so shell metacharacters stay\n  literal. Ditz trims outer stdin whitespace.\n- Treat `ready` as a snapshot and `start` as status\u002Fhistory only. Neither\n  assigns an owner, grants a lease, nor excludes another agent. Coordinate\n  ownership through the project's existing lane records or coordinator.\n- Capture exit status, stdout and stderr separately, including on failure.\n  Inspect per-item successes and errors before deciding what remains. Retry\n  only failed items whose state is known; don't replay successful closes.\n- If a mutation's receipt is lost, inspect current fields and `log_events`\n  before retrying. Comments and repeated closes append events without retry\n  deduplication. If history cannot settle the outcome, report it as unknown\n  and resolve the uncertainty before another append.\n- Distinguish a local issue change, a metadata commit, and a successful\n  `ditz sync`. Source-branch pushes do not prove metadata synchronization.\n  Use `sync` within the authorized workflow and check its actual result;\n  don't claim remote delivery from local success or an attempted push.\n\nReport the IDs changed, any per-item failures or uncertain outcomes, and the\nobserved sync state. Avoid dumping complete issue histories or private paths.\n","# Issue tracking\n\nMake the requested issue change and report what actually happened. Repository\ninstructions govern the tracker; this skill is a small workflow around the\nexisting CLI, not a new API or a replacement for project policy.\n\n## Establish the target once per context\n\nBefore mutation, identify the intended project\u002Fworktree, executable, and store:\n\n1. Check `pwd`, repository instructions, and `git rev-parse --show-toplevel`\n   (or `git worktree list` from a bare project root). Use the assigned worktree.\n2. Resolve `command -v ditz` and read `ditz --help=plain` plus the relevant\n   subcommand's help. Respect Nix\u002FBazel project tooling rules. Prefer the\n   installed executable; if absent, report it and use an explicit project-\n   approved install or `nix run github:tedks\u002Fditz -- \u003Ccmd>` fallback. Do not\n   silently switch binaries after a failure.\n3. Inspect relevant `~\u002F.ditz-config` settings and the project's documented\n   storage mode. An existing `ditz-metadata` branch takes precedence over\n   the configured issue directory; without that branch, the configured\n   directory selects the filesystem store. Correlate a known issue or project\n   identity with that store before writing. Keep private config contents out\n   of reports.\n\nIf repo instructions, config, or the observed store disagree, resolve that\nspecific mismatch before mutation. A missing binary, failed read, or empty\nlisting is not permission to run `init`, migrate beads, create a fallback\ntracker, or declare that no issues exist. Do not apply ditz commands to a\nbeads project; use its established workflow. Recheck context after changing\nproject, executable, or config; don't repeat the full preflight per issue.\n\n## Use the current command contract\n\nRead the relevant sections of the canonical\n[agent recipes](https:\u002F\u002Fgithub.com\u002Ftedks\u002Fditz\u002Fblob\u002Fmaster\u002Fdocs\u002Fagent-recipes.md)\nand [JSON\u002Fretry contract](https:\u002F\u002Fgithub.com\u002Ftedks\u002Fditz\u002Fblob\u002Fmaster\u002Fdocs\u002Fjson-contracts.md).\nPrefer their local copies in a ditz checkout when available; compare with\ninstalled command help because that binary may predate the docs. Do not invent\nflags or a common JSON envelope across commands.\n\n- Capture IDs directly with `add --ids-only`, and retain the exact ID.\n  `add --id NAME` creates once; an existing ID returns unchanged, even if new\n  creation fields differ. Inspect it before relying on its contents; use `set`\n  for an authorized update. This is not an upsert.\n- Feed multiline descriptions\u002Fcomments through the documented stdin flags\n  using a quoted here-document or owned file so shell metacharacters stay\n  literal. Ditz trims outer stdin whitespace.\n- Treat `ready` as a snapshot and `start` as status\u002Fhistory only. Neither\n  assigns an owner, grants a lease, nor excludes another agent. Coordinate\n  ownership through the project's existing lane records or coordinator.\n- Capture exit status, stdout and stderr separately, including on failure.\n  Inspect per-item successes and errors before deciding what remains. Retry\n  only failed items whose state is known; don't replay successful closes.\n- If a mutation's receipt is lost, inspect current fields and `log_events`\n  before retrying. Comments and repeated closes append events without retry\n  deduplication. If history cannot settle the outcome, report it as unknown\n  and resolve the uncertainty before another append.\n- Distinguish a local issue change, a metadata commit, and a successful\n  `ditz sync`. Source-branch pushes do not prove metadata synchronization.\n  Use `sync` within the authorized workflow and check its actual result;\n  don't claim remote delivery from local success or an attempted push.\n\nReport the IDs changed, any per-item failures or uncertain outcomes, and the\nobserved sync state. Avoid dumping complete issue histories or private paths.\n",{"name":5,"description":7},"master","f233dc9c278370625755a94f72c1ee3815214b89","skills\u002Fissue-tracking","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Ftedks","https:\u002F\u002Ftedks.com","2026-11-03 02:32:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add tedks\u002Fagent-skills --skill issue-tracking",{"tool":37,"command":38},"bunx","bunx skills add tedks\u002Fagent-skills --skill issue-tracking",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tedks\u002Fagent-skills --skill issue-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"evals\u002Fevals.json","REFERENCE","参考文档",2558,"https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002Fevals\u002Fevals.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Ffixtures\u002Fcontext-conflict.json",491,"https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002Fevals\u002Ffixtures\u002Fcontext-conflict.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Ffixtures\u002Fcreate-update.json",521,"https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002Fevals\u002Ffixtures\u002Fcreate-update.json",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"evals\u002Ffixtures\u002Fpartial-unknown.json",978,"https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002Fevals\u002Ffixtures\u002Fpartial-unknown.json",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002FREADME.md",2189,"https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fissue-tracking\u002Fevals\u002FREADME.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EME6XZ35HJRKWWKGM3TCF4","where","Use before any find, rg, grep or Glob over a repo or a directory you do not already have an exact path for. Prints a small map of the current project (root, worktrees, depth-2 tree with sizes, the repo's own \"Project structure\" notes) so you search the worktree you own with a path instead of enumerating ~, ~\u002FProjects, \u002F, \u002Fnix or \u002Ftmp.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fwhere\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EME20D4MY2J5NMD9XMH4HP","usage","Use when a CTO or lead asks how much its lanes are spending, which session is burning quota, whether a lane tripped the token tripwire, or where the provider quota meters stand. Reads the installed token-usage counts (turns\u002Fh, cached tokens\u002Fh, average context per turn for each session; per-project\u002Fmodel totals; quota meters) and the tripwire's open incidents. Counts only; never message content. Does not install anything or change thresholds.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fusage\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EMDZKTR8RD7QM6TB5SYWRZ","stacked-prs","Detailed workflow for managing stacked PRs. Use when rebasing a PR stack, resolving merge conflicts in a stack, merging stacked PRs, or when user mentions \"stack\" and \"PR\" together.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fstacked-prs\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7EMDVP1P5RNE1S6VYGWPNFW","spawn-agent","Spawn AI agents in steerable tmux windows for parallel or long-running work, including transcript-preserving Codex session forks with step-scoped compaction and structured final-recap handoffs. Use to spawn interactive agents, steer running tmux agents, or fork a Codex session for a separate step.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fspawn-agent\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7EMDR15E49C5D52XRJ52PK7","retire-agent","Preserve a private, resumable agent handoff and verify a polite exit, or transfer the handoff to a freshly spawned successor.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fretire-agent\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7EMDJYJR0EF8QG0XN0GCV7T","lean-automation","Diagnose and prevent CI\u002Fdeploy latency caused by automation inheriting a human's environment. Use when CI or a deploy feels slow, when auditing a repo's pipeline, when adding a dependency to a shared dev environment (flake devShell, base image, requirements file), or when writing a guard that is supposed to keep an environment lean.","https:\u002F\u002Fgithub.com\u002Ftedks\u002Fagent-skills\u002Fblob\u002Fmaster\u002Fskills\u002Flean-automation\u002FSKILL.md",[],[]]