rajbos
- 17 skills
- 0 followers
- 1 week ago last updated
- ▌ Sync Host Views · rajbosKeep the Visual Studio and JetBrains webview views (screens) in sync with the VS Code views, while preserving the exact set of views each host ships. Detects views added to the VS Code extension (vscode-extension/esbuild.js entryPoints) that the Visual Studio host (CopilotTokenTracker.csproj + committed webview/*.js) or JetBrains host (jetbrains-plugin/build.gradle.kts) do not yet ship, and surfaces them for a human decision instead of auto-adding. Also refreshes the committed Visual Studio bundles from a fresh dist build so existing views stay current. Use after building/updating the VS Code webviews, before a Visual Studio or JetBrains release, or whenever a host shows stale screens.
- ▌ Session Log Data · rajbosDescribes the data files available in the coding agent environment after copilot-setup-steps runs. Use when analyzing downloaded session logs or aggregated usage data.
- ▌ Visual View Diff · rajbosRender the VS Code extension's webview panels headlessly and detect which ones changed visually, producing before/after/diff screenshots for review. Use when a change touches webview UI (src/webview/**, view HTML in extension.ts, shared CSS) and you want to see and show what it looks like, or to check that a refactor changed nothing visually.
- ▌ Refresh JSON Data · rajbosRefresh token estimator and model pricing JSON files with latest data from AI model providers
- ▌ Whats New Catalog · rajbosKeep the What's New release catalog (vscode-extension/src/whatsNew/catalog.ts) in step with what the extension actually ships. Detects a released version with no catalog entry, an entry left marked "Unreleased" after it shipped, a feature pointing at a view or tab that no longer exists (a "Take me there" button that goes nowhere), and a catalogued tab on a view that never reports being opened — which silently breaks the "don't announce what they already found" rule. Also prints the surface inventory and the CHANGELOG's Unreleased bullets side by side, the two things you read when writing a new entry. Use when bumping the extension version or cutting a release, after adding a new view/tab/section, or when the What's New view looks stale or wrong.
- ▌ Azure Storage Loader · rajbosLoad token usage data from Azure Table Storage for faster iteration and analysis in chat conversations
- ▌ Copilot Log Analysis · rajbosAnalyzing GitHub Copilot session log files to extract token usage, model information, and interaction data. Use when working with session files, understanding the extension's log analysis methods, or debugging token tracking issues.
- ▌ Improve Tool Families · rajbosAnalyze coverage of the vscode-extension's tool-family definitions (DEFAULT_TOOL_FAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a live agent tool list, and suggest which family missing tool names likely belong to. Use when the Tool Output Token Analysis tab shows too many tools bucketed under "Other Tools", after adding a new editor adapter, after a new agent/CLI's tool list grows, or when asked to improve/expand the preconfigured tool families.
- ▌ Validate Editor Names · rajbosFind all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return matching friendly display names for the same path patterns, and confirm every CLI-returned name appears in the EDITOR_ICON_MAP in formatUtils.ts. Use after adding a new editor adapter, after CLI changes, or if JetBrains/other CLI-based consumers show raw editor keys instead of friendly names.
- ▌ Validate App DB Schema · rajbosValidate that ~/.copilot/data.db has the required schema for session hierarchy (workspace_parent_links, workspaces, sessions tables and columns). Runs an actual today's-data query so schema regressions are caught early. Use when data.db schema changes may have broken hierarchy enrichment, or on a periodic schedule to detect breaking changes.
- ▌ Validate Model Pricing · rajbosFind all model IDs referenced in local AI-coding session log files and debug logs, then compare them against the keys in src/modelPricing.json. Reports models found in logs that have no pricing entry (unknown — informational only) and pricing entries never observed locally (unused). Use after adding a new model to modelPricing.json, after seeing unexpected cost attributions, or to discover which new models have appeared in recent sessions. Depends on file discovery patterns from the validate-session-schemas skill.
- ▌ Refactor Large Function · rajbosPick one large function flagged by ESLint max-lines-per-function and refactor it into smaller, focused helpers without breaking tests.
- ▌ Validate Session Schemas · rajbosLoop over recent local AI-coding session log files for every supported file-based platform (Copilot Chat, Copilot CLI, JetBrains, Claude Code, Gemini CLI, Antigravity, OpenCode) and validate they still match the documented schema, while surfacing newly-discovered fields we could start using. Use after an editor/CLI update, when adding a parser, or on a schedule to catch schema drift early.
- ▌ Discover Debug Log Schema · rajbosEnumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage/*/GitHub.copilot-chat/debug-logs/*/main.jsonl) from files on the current machine — every event type and field, flagged by whether this repo reads it — and verify the exact-AIU billing contract the extension depends on is still intact. Use after a Copilot Chat update, when exact costs look wrong or have silently become estimates, or to find event types and fields we could start using.
- ▌ Check Urls · rajbosFind all hardcoded URLs in TypeScript source files and verify they resolve (return HTTP 2xx/3xx). Use when you want to validate that links in tips, hints, and documentation strings are still live.
- ▌ Pr Risk Review · rajbosAssess the risk of a changeset (a PR, a branch, or the working tree) and classify it as low, medium, or high with a written rationale. Use when reviewing a pull request for blast radius, when asked "how risky is this change", or when the PR Risk Review workflow runs the review in CI.
- ▌ Load Cache Data · rajbosLoad and display the last 10 cache entries as raw JSON output. DO NOT create extra files or pretty-print the data - output raw JSON only. Use when you need to understand cached session statistics, debug cache behavior, or work with actual cached data.