vitepress-theme-link

Run pnpm commands for this monorepo. Use this skill whenever the user asks to install dependencies, add/remove/update packages, run dev/build/test scripts, or manage the pnpm workspace — whether they say "pnpm", "装包", "加依赖", "更新依赖", "add dependency", "install package", "run script", "dev", "build", "clean", or any package-management operation. Also use it when the user is unsure which command to use or what a root script does.

Run the right local and CI-aligned validation checks for this pnpm monorepo. Use this skill whenever the user asks to test changes, run unit tests, run related e2e tests, verify a branch locally, prepare for PR/CI, or says phrases like "跑测试", "本地验证", "unit/e2e", "相关 e2e", "test check", "CI 检查", "改完跑一下测试", "不要全量 e2e", or asks which checks should be run. For quick local validation, run root unit tests and only related Playwright e2e specs; for PR/CI confidence, align with .github/workflows/ci.yml: lint, E2E coverage, typecheck, build, package artifact validation, unit tests, and related E2E specs unless full E2E is explicitly requested or clearly necessary.

Full git workflow from unstaged changes to a merged PR. Use this skill whenever the user wants to turn current changes into a GitHub issue, proper branch, commit, quality gate, and pull request — especially when they say things like "提交并提 PR", "create an issue and PR for these changes", "按照改动建 issue 提 pr", "push these changes with a proper issue", or any request that involves creating an issue and PR from working-tree changes. This skill orchestrates the tool-git-issues, tool-git-commit, tool-test-check, and CI skills into a single workflow, and it must bring in std-antfu-vue when PR changes touch Vue SFCs, theme Vue components, NewLayout.vue, Composition API, props/emits, composables, or Vue UI refactors.

Use this coding-standard skill for Vue work in this VitePress Theme Link repo, especially when editing .vue SFCs, NewLayout.vue, theme components, Composition API logic, props/emits contracts, composables, UI behavior, or Vue refactors. It adapts antfu/skills@vue-best-practices: keep the full reference-driven workflow, but preserve this repo's existing Prettier/ESLint setup, avoid unnecessary abstraction, and require related/full E2E validation for UI changes.

Control a headless Playwright Chromium browser to inspect live DOM, CSS computed styles, take screenshots, and evaluate JavaScript on any URL. Use this skill whenever the agent needs to verify VitePress SSR/hydration, inspect UnoCSS generated classes, debug plugin client-side behavior, check responsive layout or dark mode, extract DOM/CSS design tokens from external websites (GitHub, blogs, etc.), or answer questions about how a page actually renders. Triggers on: "inspect the DOM", "check the rendered HTML", "take a screenshot", "get computed styles", "what CSS does this use", "how does this page render", "browser inspect", "playwright explore", "evaluate in browser", "open in browser", "看看这个页面的样式", "截图", "检查 DOM", "浏览器看一下", and any request to extract live page information that static file reading cannot provide.

Script-driven synchronization between local Markdown issues under .ai_dev/issues and a GitHub Projects Kanban board using gh project / GraphQL. Use this skill whenever the user asks to sync kanban, GitHub Projects, project board columns, .ai_dev/issues, local issue files, pull remote issues into local markdown, push local issues to the project board, or map local issue status to remote Kanban status. Prefer the bundled scripts over ad-hoc shell commands: pull means remote overwrites local after human confirmation, push means local overwrites remote after reviewing the generated plan.

Start a local VitePress preview server to visually inspect AI changes. Use this skill whenever the user asks to preview, start a dev server, see the result of changes, run a local preview, check the site in a browser, or wants to visually verify modifications — whether they say "预览", "起一下服务", "看看效果", "打开预览", "start preview", "run dev server", "preview the site", "起个预览", or any request to inspect rendered output. Also use it when the user finishes a code change and wants to see the visual result, or when the PR workflow needs a production-build preview for human review.

Use this skill whenever PR work is finished, a PR has been created or merged, or the user says post-pr, after PR, cleanup branch, switch back to master, pull latest, clean stale dev server, clean pnpm dev, or wants to reset the local repo after a PR. It safely returns to the base branch, checks for uncommitted work and conflict states before switching, fast-forward pulls the latest base, and cleans repository-scoped watcher/dev processes such as pnpm dev, VitePress, vite, tsup, cpx, esbuild, and Playwright preview leftovers.

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.

Generate Conventional Commits messages by analyzing git diff, merge base, and branch history. Use this skill whenever the user asks to write, generate, or draft a commit message — whether they say "帮我写 commit", "generate a commit message", "draft a commit", "what should I commit", or any request involving git commit message generation. Also use it when the user is about to commit changes and needs help phrasing the message.

Check GitHub Actions CI status and fetch workflow run logs for pull requests. Use this skill whenever the user asks about CI/CD status, wants to see if a PR's checks passed or failed, needs to pull workflow logs for debugging, or mentions "ci", "pipeline", "workflow run", "checks", "GitHub Actions", "actions", "CI/CD". Triggers on phrases like "看下 ci", "ci 状态", "check CI", "pipeline 过了没", "拉 CI 日志", "拉取日志到本地", "workflow status", or any request to inspect GitHub Actions results. Also triggers after pushing to a PR branch when the user wants to verify CI results.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Scan .agents/skills/ and generate matching command wrappers in .agents/commands/. Use when adding a new skill, renaming a skill, or auditing that every skill has a corresponding command. Also use when a skill directory structure changes (e.g. flat file to directory with SKILL.md).