[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3MEXMP2AG3J4XH1K69NZF":3,"skill-same:01M7B3MEXMP2AG3J4XH1K69NZF":66},{"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":29,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7B3MEXMP2AG3J4XH1K69NZF","clarvis-tui-product-e2e",null,"Run a comprehensive current-source Clarvis terminal-UI product audit across public journeys, visual states, integrations, failures, performance stages, and long-run stability. Use for exhaustive TUI E2E proof or broad daily-use bug hunts; use clarvis-tui-e2e-validation for one bounded journey and clarvis-performance-validation for performance-only work.","getclarvis\u002Fclarvis","getclarvis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F268562684?v=4","01M7B3KM3YS9T4PRS3EVESW45V","Clarvis","01M7B3KM4ZAH0EH74XZWE9W8WQ",14,"MIT","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clarvis-tui-product-e2e\ndescription: \"Run a comprehensive current-source Clarvis terminal-UI product audit across public journeys, visual states, integrations, failures, performance stages, and long-run stability. Use for exhaustive TUI E2E proof or broad daily-use bug hunts; use clarvis-tui-e2e-validation for one bounded journey and clarvis-performance-validation for performance-only work.\"\n---\n\n# Clarvis TUI product E2E\n\nProduce an explicit feature-to-scenario ledger and enough evidence to find defects that make normal\nClarvis use slow, confusing, unsafe, unreliable, or visually unstable. A full audit is not a large\nunit-test run: it drives the current checkout in a real PTY, inspects what the user sees, exercises\nstateful integrations and failures, and repeats the critical journeys against the rebuilt bundle.\n\n## Keep the inventory current\n\nTreat [the coverage matrix](references\u002Fcoverage-matrix.md) as a maintained baseline, not as authority\nover the current product. Before every full audit, reconcile it with:\n\n- `packages\u002Fcode\u002Fsrc\u002Fapp\u002Fcommands.tsx`, `packages\u002Fcode\u002Fsrc\u002Fkeys\u002Fcommands.ts`, and dynamic skill or MCP\n  prompt registrations for the live command catalog;\n- `packages\u002Fcode\u002Fsrc\u002Fviews\u002Fconfig\u002Fhub-items.ts` and the concrete views for settings and domain hubs;\n- `packages\u002Fcode\u002Fsrc\u002Fcli-args.ts`, `packages\u002Fcode\u002Fsrc\u002Fapp\u002Flayout.ts`, keyboard policy, startup routing,\n  and transcript\u002Finput implementations;\n- `packages\u002Fcode\u002FREADME.md`, current tests, artifact tooling, and `specs\u002Fknown-issues.md` for operational\n  behavior and environmental signatures.\n\nAdd, remove, rename, or split scenarios when those sources change. Never keep a scenario merely to\nmake an old checklist look complete, and never omit a live user route because the matrix predates it.\n\n`sync-doc` maintenance rule: whenever documentation synchronization finds or applies a user-visible\nTUI change, it must update this skill in the same change. Update the matrix for commands, flags,\nsettings, key or pointer behavior, user journeys, integrations, states, limits, and failure or\nrecovery behavior. Update this file when the execution or evidence method changes, and update the\nreport template when verdict semantics change.\n\nThis is static maintenance only. `sync-doc` must not launch Clarvis, build the bundle, open a PTY,\nexecute scenarios, or wait for E2E pass\u002Ffail results. A full product test is a separate invocation of\nthis skill. After updating the checklist, `sync-doc` may run this static drift check from the\nrepository root:\n\n```bash\nbun .agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Fscripts\u002Fcheck-live-inventory.ts\n```\n\nThe check compares registered commands and Settings panels with the checklist and detects duplicate\nscenario IDs. It does not test product behavior or produce an E2E verdict.\n\n## Compose the supporting skills\n\n1. Read `AGENTS.md`, inspect `git status --short`, and preserve unrelated worktree changes.\n2. Read and follow `$clarvis-tui-e2e-validation` for each interactive journey and `$tui-driver` for\n   PTY interaction, stable waits, frames, screenshots, and repeatable assertions.\n3. Read and follow `$clarvis-performance-validation` for startup, clean-versus-extension-heavy runs,\n   OAuth non-blocking behavior, lifecycle soaks, and performance interpretation.\n4. Read the coverage matrix before planning and the report template before capturing results.\n5. Run `scripts\u002Fcheck-live-inventory.ts` to catch static command and Settings drift, then manually\n   reconcile the remaining product surface before planning the E2E.\n\nIf a supporting skill is unavailable, preserve its contract locally: a real PTY, current-artifact\nprovenance, semantic checkpoints, inspected visual evidence, isolated state, and explicit limitations\nremain mandatory.\n\n## Freeze provenance and isolation\n\nRecord the branch, full commit, worktree status, Bun and OpenTUI versions, OS and architecture,\nterminal identity and dimensions, color mode, and exact launch command. Never invoke an installed\n`clarvis` release and attribute it to the checkout.\n\nUse two artifact rounds:\n\n1. **Current source:** from a disposable workspace, launch the checkout's\n   `packages\u002Fcode\u002Fsrc\u002Fcli.ts` with `CLARVIS_CODE_SOURCE=1` and diagnostics enabled.\n2. **Final bundle:** run `bun run build:code`, run `bun run smoke`, then launch the same checkout's\n   CLI without `CLARVIS_CODE_SOURCE`.\n\nUse a fresh temporary `CLARVIS_HOME` and disposable Git workspace per independent state family.\nNever copy the user's normal keys or subscription files by default. Keep fixture credentials fake,\nscrub secrets from commands and reports, and restrict destructive scenarios to test-owned paths.\nRecord retained directories; otherwise remove test-owned state and stop every PTY and child process.\n\n## Build a deterministic integration harness\n\nPrefer local, scripted fixtures before external services. The complete harness should be able to\nproduce:\n\n- streaming model text, reasoning, usage, optional cache telemetry, tool calls, elicitation,\n  compaction, malformed events, provider errors, cancellation, and a stream that never settles;\n- stateful Tasks behavior for the current `clarvis.tasks.v2` adapter, including conflict, degraded,\n  unknown-outcome, and refresh paths;\n- MCP tools and prompts, connection failure, reconnect, delayed responses, OAuth-pending behavior,\n  and mixed healthy\u002Fdegraded pools;\n- local Extension Profiles, plugins, marketplace entries, skills, hooks, executables, trust changes,\n  conflicting identities, large catalogs, and executable-file drift;\n- seeded sessions, plans, memory, workflows, delegated agents, worktrees, settings revisions, and\n  corrupt, truncated, oversized, or concurrently edited state.\n\nUse unique visible tokens for every scenario. When the repository lacks a durable fixture for an\nimportant user route, record the gap; add a reusable test harness only when implementation is within\nthe requested scope. Synthetic fixtures prove Clarvis behavior at the fixture boundary, not real\nprovider, account, browser, or physical-terminal compatibility.\n\n## Plan the proof\n\nCopy every applicable row from the coverage matrix into a run ledger. For each scenario, define:\n\n- preconditions and owned fixture state;\n- initial visible state;\n- exact keyboard or pointer actions;\n- intermediate transitions and stable readiness tokens;\n- settled behavior and persisted state;\n- visual invariants, diagnostics, and resource or timing observations;\n- cleanup and a `pass`, `fail`, `blocked`, or `unverified` verdict.\n\nDo not collapse multiple features into one broad green row. Pair a happy path with cancellation,\nfailure, recovery, stale-completion, and resize or navigation interruption wherever those states are\npossible. Test global and workspace scope plus their conflict behavior for persisted configuration.\n\n## Execute in risk order\n\n1. Prove boot, first paint, early input, onboarding or recovery, basic submission, cancellation,\n   shutdown, and source provenance.\n2. Exercise composer, navigation, all public commands, settings panels, transcript projections,\n   sessions, model and agent selection, and local shell behavior.\n3. Exercise plans, memory, tasks, workflows, subagents, tools, guard and sandbox, extensions, skills,\n   hooks, MCP, trust, storage, diagnostics, worktrees, and reconnect behavior.\n4. Inject slow, reordered, rejected, duplicated, never-settling, stale, and concurrent completions.\n   Resize, navigate, press Escape or Ctrl+C, switch sessions, and start shutdown during transitions.\n5. Run startup and overlay benchmarks, repeated complete-turn\u002Fnavigation cycles, and an idle\u002Factive\n   soak with diagnostics and process-tree memory observations.\n6. Re-run every critical journey and every fixed defect against the final rebuilt bundle.\n7. Run real-provider, browser OAuth, physical-terminal, or platform canaries only when their required\n   credentials, account actions, host access, and authorization are available. Keep their verdicts\n   separate from deterministic PTY results.\n\nPoll observable readiness and stable frames instead of sleeping for an assumed duration. Inspect\nimages for geometry, focus, clipping, hierarchy, color, flicker, stale rows, and continuity; text\nsnapshots alone cannot pass a visual requirement. Use short frame sequences around animation,\nscrolling, root replacement, and suspected redraw instability.\n\n## Hunt daily-use instability\n\nActively look for lost or duplicated input, delayed Escape, incorrect Ctrl+C ownership, stale async\nresults, frozen mutation keys, invisible progress, accidental retries, focus theft, scroll jumps,\ntranscript repaint, clipped hints, misleading status, secret exposure, scope confusion, blind\noverwrite, state corruption, unbounded listeners or owners, memory growth, orphan processes, and\nshutdown that waits on background work.\n\nUse an external watchdog for hangs and record the whole process tree separately from Clarvis's own\nRSS telemetry. Interpret startup-composer readiness, complete-app paint, kernel\u002Frun readiness, and\nrun completion as distinct stages. Treat current benchmark thresholds as environment-qualified\ncriteria and refresh them from the owning tooling before use.\n\n## Classify and report\n\nUse these user-impact levels:\n\n- **P0:** data loss or corruption, secret or trust-boundary failure, duplicate destructive action,\n  unrecoverable process failure, or security escape;\n- **P1:** routine workflow blocked, freeze or hang, lost input, wrong persistent state, crash, or no\n  usable recovery;\n- **P2:** material latency, flicker, clipping, misleading feedback, broken secondary route, or\n  repeated friction with a workaround;\n- **P3:** minor polish or low-frequency inconsistency without meaningful workflow impact.\n\nFollow [the report template](references\u002Freport-template.md). Include artifact provenance, the complete\nledger, evidence locations, defects with reproduction steps, performance samples, cleanup, and every\nenvironmental or external limitation. A complete verdict requires every matrix row to be passed,\nfailed, blocked, or unverified, no untriaged P0\u002FP1, and final-bundle repetition of the critical path.\nUnavailable external or physical canaries remain `unverified`; they never become implicit passes.\n","# Clarvis TUI product E2E\n\nProduce an explicit feature-to-scenario ledger and enough evidence to find defects that make normal\nClarvis use slow, confusing, unsafe, unreliable, or visually unstable. A full audit is not a large\nunit-test run: it drives the current checkout in a real PTY, inspects what the user sees, exercises\nstateful integrations and failures, and repeats the critical journeys against the rebuilt bundle.\n\n## Keep the inventory current\n\nTreat [the coverage matrix](references\u002Fcoverage-matrix.md) as a maintained baseline, not as authority\nover the current product. Before every full audit, reconcile it with:\n\n- `packages\u002Fcode\u002Fsrc\u002Fapp\u002Fcommands.tsx`, `packages\u002Fcode\u002Fsrc\u002Fkeys\u002Fcommands.ts`, and dynamic skill or MCP\n  prompt registrations for the live command catalog;\n- `packages\u002Fcode\u002Fsrc\u002Fviews\u002Fconfig\u002Fhub-items.ts` and the concrete views for settings and domain hubs;\n- `packages\u002Fcode\u002Fsrc\u002Fcli-args.ts`, `packages\u002Fcode\u002Fsrc\u002Fapp\u002Flayout.ts`, keyboard policy, startup routing,\n  and transcript\u002Finput implementations;\n- `packages\u002Fcode\u002FREADME.md`, current tests, artifact tooling, and `specs\u002Fknown-issues.md` for operational\n  behavior and environmental signatures.\n\nAdd, remove, rename, or split scenarios when those sources change. Never keep a scenario merely to\nmake an old checklist look complete, and never omit a live user route because the matrix predates it.\n\n`sync-doc` maintenance rule: whenever documentation synchronization finds or applies a user-visible\nTUI change, it must update this skill in the same change. Update the matrix for commands, flags,\nsettings, key or pointer behavior, user journeys, integrations, states, limits, and failure or\nrecovery behavior. Update this file when the execution or evidence method changes, and update the\nreport template when verdict semantics change.\n\nThis is static maintenance only. `sync-doc` must not launch Clarvis, build the bundle, open a PTY,\nexecute scenarios, or wait for E2E pass\u002Ffail results. A full product test is a separate invocation of\nthis skill. After updating the checklist, `sync-doc` may run this static drift check from the\nrepository root:\n\n```bash\nbun .agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Fscripts\u002Fcheck-live-inventory.ts\n```\n\nThe check compares registered commands and Settings panels with the checklist and detects duplicate\nscenario IDs. It does not test product behavior or produce an E2E verdict.\n\n## Compose the supporting skills\n\n1. Read `AGENTS.md`, inspect `git status --short`, and preserve unrelated worktree changes.\n2. Read and follow `$clarvis-tui-e2e-validation` for each interactive journey and `$tui-driver` for\n   PTY interaction, stable waits, frames, screenshots, and repeatable assertions.\n3. Read and follow `$clarvis-performance-validation` for startup, clean-versus-extension-heavy runs,\n   OAuth non-blocking behavior, lifecycle soaks, and performance interpretation.\n4. Read the coverage matrix before planning and the report template before capturing results.\n5. Run `scripts\u002Fcheck-live-inventory.ts` to catch static command and Settings drift, then manually\n   reconcile the remaining product surface before planning the E2E.\n\nIf a supporting skill is unavailable, preserve its contract locally: a real PTY, current-artifact\nprovenance, semantic checkpoints, inspected visual evidence, isolated state, and explicit limitations\nremain mandatory.\n\n## Freeze provenance and isolation\n\nRecord the branch, full commit, worktree status, Bun and OpenTUI versions, OS and architecture,\nterminal identity and dimensions, color mode, and exact launch command. Never invoke an installed\n`clarvis` release and attribute it to the checkout.\n\nUse two artifact rounds:\n\n1. **Current source:** from a disposable workspace, launch the checkout's\n   `packages\u002Fcode\u002Fsrc\u002Fcli.ts` with `CLARVIS_CODE_SOURCE=1` and diagnostics enabled.\n2. **Final bundle:** run `bun run build:code`, run `bun run smoke`, then launch the same checkout's\n   CLI without `CLARVIS_CODE_SOURCE`.\n\nUse a fresh temporary `CLARVIS_HOME` and disposable Git workspace per independent state family.\nNever copy the user's normal keys or subscription files by default. Keep fixture credentials fake,\nscrub secrets from commands and reports, and restrict destructive scenarios to test-owned paths.\nRecord retained directories; otherwise remove test-owned state and stop every PTY and child process.\n\n## Build a deterministic integration harness\n\nPrefer local, scripted fixtures before external services. The complete harness should be able to\nproduce:\n\n- streaming model text, reasoning, usage, optional cache telemetry, tool calls, elicitation,\n  compaction, malformed events, provider errors, cancellation, and a stream that never settles;\n- stateful Tasks behavior for the current `clarvis.tasks.v2` adapter, including conflict, degraded,\n  unknown-outcome, and refresh paths;\n- MCP tools and prompts, connection failure, reconnect, delayed responses, OAuth-pending behavior,\n  and mixed healthy\u002Fdegraded pools;\n- local Extension Profiles, plugins, marketplace entries, skills, hooks, executables, trust changes,\n  conflicting identities, large catalogs, and executable-file drift;\n- seeded sessions, plans, memory, workflows, delegated agents, worktrees, settings revisions, and\n  corrupt, truncated, oversized, or concurrently edited state.\n\nUse unique visible tokens for every scenario. When the repository lacks a durable fixture for an\nimportant user route, record the gap; add a reusable test harness only when implementation is within\nthe requested scope. Synthetic fixtures prove Clarvis behavior at the fixture boundary, not real\nprovider, account, browser, or physical-terminal compatibility.\n\n## Plan the proof\n\nCopy every applicable row from the coverage matrix into a run ledger. For each scenario, define:\n\n- preconditions and owned fixture state;\n- initial visible state;\n- exact keyboard or pointer actions;\n- intermediate transitions and stable readiness tokens;\n- settled behavior and persisted state;\n- visual invariants, diagnostics, and resource or timing observations;\n- cleanup and a `pass`, `fail`, `blocked`, or `unverified` verdict.\n\nDo not collapse multiple features into one broad green row. Pair a happy path with cancellation,\nfailure, recovery, stale-completion, and resize or navigation interruption wherever those states are\npossible. Test global and workspace scope plus their conflict behavior for persisted configuration.\n\n## Execute in risk order\n\n1. Prove boot, first paint, early input, onboarding or recovery, basic submission, cancellation,\n   shutdown, and source provenance.\n2. Exercise composer, navigation, all public commands, settings panels, transcript projections,\n   sessions, model and agent selection, and local shell behavior.\n3. Exercise plans, memory, tasks, workflows, subagents, tools, guard and sandbox, extensions, skills,\n   hooks, MCP, trust, storage, diagnostics, worktrees, and reconnect behavior.\n4. Inject slow, reordered, rejected, duplicated, never-settling, stale, and concurrent completions.\n   Resize, navigate, press Escape or Ctrl+C, switch sessions, and start shutdown during transitions.\n5. Run startup and overlay benchmarks, repeated complete-turn\u002Fnavigation cycles, and an idle\u002Factive\n   soak with diagnostics and process-tree memory observations.\n6. Re-run every critical journey and every fixed defect against the final rebuilt bundle.\n7. Run real-provider, browser OAuth, physical-terminal, or platform canaries only when their required\n   credentials, account actions, host access, and authorization are available. Keep their verdicts\n   separate from deterministic PTY results.\n\nPoll observable readiness and stable frames instead of sleeping for an assumed duration. Inspect\nimages for geometry, focus, clipping, hierarchy, color, flicker, stale rows, and continuity; text\nsnapshots alone cannot pass a visual requirement. Use short frame sequences around animation,\nscrolling, root replacement, and suspected redraw instability.\n\n## Hunt daily-use instability\n\nActively look for lost or duplicated input, delayed Escape, incorrect Ctrl+C ownership, stale async\nresults, frozen mutation keys, invisible progress, accidental retries, focus theft, scroll jumps,\ntranscript repaint, clipped hints, misleading status, secret exposure, scope confusion, blind\noverwrite, state corruption, unbounded listeners or owners, memory growth, orphan processes, and\nshutdown that waits on background work.\n\nUse an external watchdog for hangs and record the whole process tree separately from Clarvis's own\nRSS telemetry. Interpret startup-composer readiness, complete-app paint, kernel\u002Frun readiness, and\nrun completion as distinct stages. Treat current benchmark thresholds as environment-qualified\ncriteria and refresh them from the owning tooling before use.\n\n## Classify and report\n\nUse these user-impact levels:\n\n- **P0:** data loss or corruption, secret or trust-boundary failure, duplicate destructive action,\n  unrecoverable process failure, or security escape;\n- **P1:** routine workflow blocked, freeze or hang, lost input, wrong persistent state, crash, or no\n  usable recovery;\n- **P2:** material latency, flicker, clipping, misleading feedback, broken secondary route, or\n  repeated friction with a workaround;\n- **P3:** minor polish or low-frequency inconsistency without meaningful workflow impact.\n\nFollow [the report template](references\u002Freport-template.md). Include artifact provenance, the complete\nledger, evidence locations, defects with reproduction steps, performance samples, cleanup, and every\nenvironmental or external limitation. A complete verdict requires every matrix row to be passed,\nfailed, blocked, or unverified, no untriaged P0\u002FP1, and final-bundle repetition of the critical path.\nUnavailable external or physical canaries remain `unverified`; they never become implicit passes.\n",{"name":5,"description":7},"main","17a550a7fff59752a1917c3c88dbe9a2aef09bdf",".agents\u002Fskills\u002Fclarvis-tui-product-e2e",1,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis","https:\u002F\u002Fclarvis.dev","https:\u002F\u002Fgithub.com\u002Fgetclarvis","2026-10-05 05:46:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add getclarvis\u002Fclarvis --skill clarvis-tui-product-e2e",{"tool":38,"command":39},"bunx","bunx skills add getclarvis\u002Fclarvis --skill clarvis-tui-product-e2e",{"tool":41,"command":42},"pnpm","pnpm dlx skills add getclarvis\u002Fclarvis --skill clarvis-tui-product-e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",271,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcoverage-matrix.md",26782,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Freferences\u002Fcoverage-matrix.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Freport-template.md",4462,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Freferences\u002Freport-template.md",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fcheck-live-inventory.ts","SCRIPT","脚本",2865,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-product-e2e\u002Fscripts\u002Fcheck-live-inventory.ts",[67,74,81,88,95,102],{"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},"01M7B3N824S0ABTQWA2A2QANGN","suppressed","Reconcile an invoice ledger.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fsuppressed\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},"01M7B3N4Z5VMSJH4W3CDVMP08S","slash-hidden","Rebuild the search index.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fslash-hidden\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},"01M7B3N3AG6C6PKRGV6VK0FREX","presented","Draft release notes from a commit range.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fpresented\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7B3N1TX6H3K4QYTDGQ0ZJT2","plain","Format a changelog entry.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fplain\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7B3N0CKN3VWF13VBBT5CKX6","no-name","Bisect a regression across a commit range.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fno-name\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7B3MX6DG19B3S2QD6RKX8QC","no-description","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fno-description\u002FSKILL.md",[],[]]