[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEPZEB9ZXWAQE05KZ4MEAM":3,"skill-same:01M7DEPZEB9ZXWAQE05KZ4MEAM":45},{"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DEPZEB9ZXWAQE05KZ4MEAM","review-bugbot",null,"Review code changes with Bugbot subagent.","odellsallis93\u002Fskills-repo","odellsallis93","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87449759?v=4","01M7DEG0QK6S7ZF5TAZZH1JKT9","ODell Sallis","01M7DEG0R9VYQBMCTWBFXHBZDS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fplugins\u002Fodell-codex\u002Fskills\u002Freview-bugbot\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-bugbot\ndescription: Review code changes with Bugbot subagent.\n---\n# Review Bugbot\n\nUse this skill when the user asks to run `\u002Freview-bugbot`.\n\nLaunch exactly one `bugbot` subagent with:\n\n- `run_in_background: false` unless explicitly asked to run in background\n- `description: \"Bugbot\"`\n- `subagent_type: \"bugbot\"`\n\nThe review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.\n\nBy default, the review subagent infers the repository's actual base branch, such as `main`, when computing `branch changes`. In most cases, do not provide `Base Branch`. Only provide it if you know the current branch or PR should be compared against a specific branch other than the repository's default base branch, such as when you created the current branch from another branch.\n\nSpecial case: if the user explicitly asks to review a specific PR or branch, make sure that target is checked out before launching the subagent:\n- Examples include `github.com\u002F... \u002Freview`, `review {link}`, or `review {branch-name}`.\n- Resolve the provided PR link, PR number, or branch name to the PR head branch or named branch.\n- Check whether the target branch is already the currently checked out local branch. If it is, continue.\n- If a different branch is currently checked out, try to switch to the target branch.\n- If Git refuses to switch because local files would be overwritten, conflicts need resolution, or another checkout blocker occurs, explain the blocker and ask whether the user wants to stash local changes before retrying.\n- Only stash after the user confirms. If the stash succeeds, retry switching to the target branch.\n- Launch the review subagent only after the target branch is checked out locally.\n\nUse this exact prompt shape:\n\n```text\nFull Repository Path: \u003Cabsolute repository path>\nDiff: \u003Cone of: \"branch changes\", \"uncommitted changes\", \"natural language\">\nBase Branch: \u003Conly include this line when reviewing branch changes against a known specific base branch>\nChange Description: \u003Crequired only when Diff is \"natural language\"; list each changed file and what changed in it>\nCustom Instructions: \u003Conly include this line when the user gave specific review instructions>\n```\n\nDefault to `branch changes`, which reviews branch changes against the merge-base with the default\u002Fbase branch, including committed, staged, and unstaged changes. If the user asks to review only uncommitted, local working tree, dirty, or not-yet-committed changes, use `uncommitted changes`.\n\nIf the review subagent fails before producing findings, inspect the failure text.\n\n- If the failure is caused by calling the subagent incorrectly, such as a missing `Full Repository Path`, missing `Diff`, wrong prompt shape, or wrong subagent type, correct the invocation and retry it once immediately.\n- If the subagent reports it could not compute the diff (for example an empty diff, missing diff metadata, or that it could not compute the diff), retry once with `Diff: natural language`, omitting `Base Branch` and providing a `Change Description`. The subagent will read those files directly. Only use this as a last resort, after the regular diff-based review has failed because the diff could not be computed.\n\n  Write the `Change Description` as one block per changed file: a `\u003Cpath> (added|modified|deleted|renamed)` header followed by bullet points of what changed. Mention line numbers or ranges inline where they help and you know them (for example `(L40-58)` or `around L120`); they are optional, not required on every bullet. Example:\n\n  ```text\n  src\u002Fauth\u002Flogin.ts (modified):\n  - rewrote validateSession (L40-58) to check token expiry before the DB lookup\n  - removed the fallback that accepted empty tokens\n\n  src\u002Fauth\u002Flegacy.ts (deleted)\n\n  src\u002Fauth\u002Fmfa.ts (added):\n  - new verifyMfaCode() (L1-30) that calls the TOTP service and rate-limits attempts\n  ```\n- For any other subagent failure, retry once with the same prompt shape.\n- If the same failure persists after the retry, stop. Briefly tell the user that the review subagent could not complete and include the short error or blocker. Do not keep retrying.\n\nAfter the subagent finishes, summarize the result:\n\n- If it reports that no diff was found or the diff is empty, tell the user in one sentence that there was no diff to review.\n- If it found no issues, give a one-line status such as \"Bugbot found 2 findings \u002F Bugbot found no bugs\".\n- If it found issues, print a compact markdown table with one row per finding, sorted by severity (highest first), using exactly these columns: Severity, Location (file:line), Finding. Put the file and line in the location column as `file:line`.\n\nDo not fix findings or rerun review unless the user explicitly asks for that next step.\n","# Review Bugbot\n\nUse this skill when the user asks to run `\u002Freview-bugbot`.\n\nLaunch exactly one `bugbot` subagent with:\n\n- `run_in_background: false` unless explicitly asked to run in background\n- `description: \"Bugbot\"`\n- `subagent_type: \"bugbot\"`\n\nThe review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.\n\nBy default, the review subagent infers the repository's actual base branch, such as `main`, when computing `branch changes`. In most cases, do not provide `Base Branch`. Only provide it if you know the current branch or PR should be compared against a specific branch other than the repository's default base branch, such as when you created the current branch from another branch.\n\nSpecial case: if the user explicitly asks to review a specific PR or branch, make sure that target is checked out before launching the subagent:\n- Examples include `github.com\u002F... \u002Freview`, `review {link}`, or `review {branch-name}`.\n- Resolve the provided PR link, PR number, or branch name to the PR head branch or named branch.\n- Check whether the target branch is already the currently checked out local branch. If it is, continue.\n- If a different branch is currently checked out, try to switch to the target branch.\n- If Git refuses to switch because local files would be overwritten, conflicts need resolution, or another checkout blocker occurs, explain the blocker and ask whether the user wants to stash local changes before retrying.\n- Only stash after the user confirms. If the stash succeeds, retry switching to the target branch.\n- Launch the review subagent only after the target branch is checked out locally.\n\nUse this exact prompt shape:\n\n```text\nFull Repository Path: \u003Cabsolute repository path>\nDiff: \u003Cone of: \"branch changes\", \"uncommitted changes\", \"natural language\">\nBase Branch: \u003Conly include this line when reviewing branch changes against a known specific base branch>\nChange Description: \u003Crequired only when Diff is \"natural language\"; list each changed file and what changed in it>\nCustom Instructions: \u003Conly include this line when the user gave specific review instructions>\n```\n\nDefault to `branch changes`, which reviews branch changes against the merge-base with the default\u002Fbase branch, including committed, staged, and unstaged changes. If the user asks to review only uncommitted, local working tree, dirty, or not-yet-committed changes, use `uncommitted changes`.\n\nIf the review subagent fails before producing findings, inspect the failure text.\n\n- If the failure is caused by calling the subagent incorrectly, such as a missing `Full Repository Path`, missing `Diff`, wrong prompt shape, or wrong subagent type, correct the invocation and retry it once immediately.\n- If the subagent reports it could not compute the diff (for example an empty diff, missing diff metadata, or that it could not compute the diff), retry once with `Diff: natural language`, omitting `Base Branch` and providing a `Change Description`. The subagent will read those files directly. Only use this as a last resort, after the regular diff-based review has failed because the diff could not be computed.\n\n  Write the `Change Description` as one block per changed file: a `\u003Cpath> (added|modified|deleted|renamed)` header followed by bullet points of what changed. Mention line numbers or ranges inline where they help and you know them (for example `(L40-58)` or `around L120`); they are optional, not required on every bullet. Example:\n\n  ```text\n  src\u002Fauth\u002Flogin.ts (modified):\n  - rewrote validateSession (L40-58) to check token expiry before the DB lookup\n  - removed the fallback that accepted empty tokens\n\n  src\u002Fauth\u002Flegacy.ts (deleted)\n\n  src\u002Fauth\u002Fmfa.ts (added):\n  - new verifyMfaCode() (L1-30) that calls the TOTP service and rate-limits attempts\n  ```\n- For any other subagent failure, retry once with the same prompt shape.\n- If the same failure persists after the retry, stop. Briefly tell the user that the review subagent could not complete and include the short error or blocker. Do not keep retrying.\n\nAfter the subagent finishes, summarize the result:\n\n- If it reports that no diff was found or the diff is empty, tell the user in one sentence that there was no diff to review.\n- If it found no issues, give a one-line status such as \"Bugbot found 2 findings \u002F Bugbot found no bugs\".\n- If it found issues, print a compact markdown table with one row per finding, sorted by severity (highest first), using exactly these columns: Severity, Location (file:line), Finding. Put the file and line in the location column as `file:line`.\n\nDo not fix findings or rerun review unless the user explicitly asks for that next step.\n",{"name":5,"description":7},"main","1c9c71cb8682c1f18c7a54bc09a9ddfe2f70b80d","plugins\u002Fodell-codex\u002Fskills\u002Freview-bugbot","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo","https:\u002F\u002Fgithub.com\u002Fodellsallis93","SWE: Applied \u002F Agentic AI, Full-stack Web Dev, Mobile, Design | Computer Vision | Automation | Events | Music","2026-11-11 07:05:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add odellsallis93\u002Fskills-repo --skill review-bugbot",{"tool":37,"command":38},"bunx","bunx skills add odellsallis93\u002Fskills-repo --skill review-bugbot",{"tool":40,"command":41},"pnpm","pnpm dlx skills add odellsallis93\u002Fskills-repo --skill review-bugbot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fplugins\u002Fodell-codex\u002Fskills\u002Freview-bugbot\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DF09PNHXECAA9M9472985Z","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DF06BVP31PP8PB9WQBG6NR","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DF03EM39HHEET1C44R50F7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DF00MVBHP5P88V3A8FR3AW","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"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},"01M7DEZWFJTR2K5SGCVE1MQRTZ","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\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},"01M7DEZSYEBMNAGE02BCYWKMHT","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[]]