minhuw

@minhuw source repo

25 skills
0 followers
12 hours ago last updated

▌
Docmancer · minhuw
Query the Ocellus local uncore documentation RAG with Docmancer. Use when working on Intel uncore PMU events, Ocellus metrics, Grafana dashboards, CPU generation support, Linux uncore perf/sysfs behavior, Intel perfmon JSON, or any question that needs source-grounded lookup from the local `.resources/docmancer` corpus.

0
installs
▌
Quic RAG · minhuw
Use when answering QUIC protocol or RFC questions in this repository, especially section lookups, frames, transport parameters, ACK behavior, version negotiation, packet formats, error codes, or when grounded RFC citations are needed.

0
installs
▌
Gh Work Item · minhuw bundle
Create consistent GitHub issues for tracking implementation work, bug fixes, design tasks, technical debt, protocol gaps, test gaps, performance work, documentation work, CI failures, interop follow-ups, and investigations in the coquic repository. Use when asked to draft, create, batch-create, organize, or update GitHub issues for things that should be fixed, implemented, reviewed later, or tracked as project work.

0
installs
▌
Debug Interop Run · minhuw
Debug failed remote GitHub Actions Interop workflow runs for the coquic repository. Use when given a .github/workflows/interop.yml run URL or run ID and asked to inspect CI, download failed interop logs/artifacts with gh, identify failed peer/testcase/direction combinations, reproduce them locally with interop/run-official.sh, fix reproducible coquic bugs, validate, commit, push, and dispatch a fresh Interop workflow run.

0
installs
▌
Fix Code Quality Issues · minhuw
Fetch and fix current CodeQL and Codacy issues for the minhuw/coquic repository. Use when asked to inspect GitHub Security code scanning alerts at https://github.com/minhuw/coquic/security, Codacy current issues at https://app.codacy.com/gh/minhuw/coquic/issues/current, or to automatically repair static-analysis/security findings without weakening scanner configuration.

0
installs
▌
Gh Issue Implementation · minhuw bundle
Implement CoQUIC GitHub issues end to end. Use when the user gives a GitHub issue URL/number or asks to fetch, implement, test, add Duvet/RFC annotations, update issue TODO checkboxes, comment on, or close an implementation issue in the minhuw/coquic repository.

0
installs
▌
Herder Grill · minhuw bundle
Interview the user one decision at a time, investigate repository facts, maintain domain-model and ADR obligations, and create a focused validated Herder plan or dependency-aware subplan set from confirmed intent. Also refine an existing TODO or decision-blocked plan when invoked with --plan, including a manager-reserved unstarted plan during active Herder Fire. Use when the user invokes /herder-grill, wants to clarify a feature or change before implementation, asks to turn product intent into plans, or wants to grill or stress-test an existing plan.

0
installs
▌
Herder Plans · minhuw bundle
Initialize, shape, validate, inspect, snapshot, and report Herder Markdown plan graphs through Pi's native plan tool. Use when creating or repairing herder-plans/, checking dependencies and readiness, changing tracking policy, or inspecting execution statistics.

0
installs
▌
Herder Improve · minhuw bundle
Survey a codebase as a senior advisor and write prioritized, semantically bounded Herder plan graphs from verified repository findings without changing source code. Use when asked to audit code, find bugs or improvement opportunities, suggest evidence-backed product direction, or produce a herder-plans/ backlog for Herder Fire. Route user-defined new features that require intent clarification to Grill.

0
installs
▌
Herder Simplify · minhuw bundle
Survey a codebase for evidence-backed opportunities to delete or consolidate code, retire obsolete paths and abstractions, reduce state and control-flow complexity, and lower maintenance burden without changing required behavior; write prioritized, semantically bounded Herder plan graphs without modifying source. Use when the user invokes /herder-simplify or asks for a smaller, clearer, easier-to-maintain codebase and wants the work planned for Herder Fire.

0
installs
▌
Herder Validate · minhuw
Validate a Herder plan directory against the canonical mechanical and semantic contracts, report plan/index/dependency/drift issues without changing files, and conservatively repair safe issues with --fix. Use when the user invokes /herder-validate, asks whether herder-plans/ is Fire-ready or executable, wants a cold plan-quality audit, or asks to repair malformed, incomplete, or drifted plans. Do not use to execute plans, modify source code, or decide missing product intent.

0
installs
▌
Paper Validator · minhuw
This skill should be used when conducting comprehensive reviews of research papers for top-tier computer science conferences. Use for identifying weaknesses, unclear statements, missing evidence, and structural issues in academic papers. The skill autonomously reads files, searches for patterns, analyzes structure, and provides constructive peer-reviewer feedback.

0
installs
▌
Launch · minhuw bundle
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test UI features, take screenshots, set breakpoints in the renderer / extension host / main process, or combine UI driving with debugging.

0
installs
▌
UX Theming · minhuw
VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC/focus compliance.

0
installs
▌
Smoke Tests · minhuw
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.

0
installs
▌
Sweeper Fix · minhuw
Implement a VS Code Sweeper fix spec — fetch the sweeper's agent-fixable review record from its public state repo, implement the narrow fix in the current vscode checkout, and — after showing the diff — open a draft PR. Use ONLY when the request explicitly asks for the sweeper — "sweeper-fix", "sweeper", "vscodesweeper", a sweeper record, or a sweeper fix spec. Do NOT use for a plain "fix this issue" request that doesn't mention the sweeper; fix those directly with your normal tools instead.

0
installs
▌
Accessibility · minhuw
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

0
installs
▌
UX CSS Layout · minhuw
VS Code CSS conventions, file organization, class naming, standard sizes, SplitView/Grid layout, scrollable content, responsive layout, and text overflow/ellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues.

0
installs
▌
Design Philosophy · minhuw
The VS Code design philosophy — a shared Values→Principles→Moves vocabulary for reasoning about UI in design terms instead of raw pixels. Use when designing, building, reviewing, or giving feedback on any visual surface; when deciding a radius, spacing, type role, icon size, border, color, or motion; or when translating a "this feels off" observation into a concrete, principled fix.

0
installs
▌
Flaky Smoke Tests · minhuw
Diagnose intermittent VS Code Electron smoke-test failures from the Azure DevOps Flaky Smoke Tests pipeline (definition 700). Covers finding failed iterations, downloading task logs and platform artifacts with Azure CLI, correlating cumulative runner logs, tracing the introducing commit, and queueing focused validation runs.

0
installs
▌
Integration Tests · minhuw
Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.

0
installs
▌
Update Screenshots · minhuw
Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR. Use when asked to update, accept, or refresh component screenshot baselines from CI. This skill should be run as a subagent.

0
installs
▌
Validate UI Scenario · minhuw
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.

0
installs
▌
Vscode Dev Workbench · minhuw
Use when the user wants to run the vscode.dev server locally and exercise the VS Code web workbench in the integrated browser against local VS Code sources. Covers starting the dev server, the `vscode-quality=dev` URL, browser-driven interaction patterns, mobile emulation, reloads, and troubleshooting.

0
installs
▌
Policy And Managed Settings · minhuw bundle
Use whenever adding, modifying, or reviewing any Copilot, agent, LLM, AI, tool, permission, sandbox, MCP, model, telemetry, feature-gate, setting, configuration, or enterprise control—especially anything an organization or administrator may need to manage. Start here to decide whether it belongs in runtime managed settings, a typed SDK contract, VS Code configuration policy, extension policy, or a split implementation. Run on every new Copilot/agent/LLM control and ANY change that adds a `policy:` field.

0
installs

25 published skills