MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: B站/bilibili, V2EX, GitHub code search, YouTube, RSS feeds, or any web URL. 7 no-login…
Design public interfaces for libraries and tools that other people depend on. Use when designing or reviewing a public API surface, deciding what to export, naming functions and CLI flags, adding configuration options, planning deprecations, or when the user asks "is this a good API" or "how do I change this without…
Review a pull request the way a good open-source maintainer does. Use when reviewing an incoming PR, when the user asks "review this PR" or "is this ready to merge", when triaging a stale PR queue, or when writing review feedback to an external contributor. Covers what to check and in what order, severity levels…
Turn users into contributors and make their first PR succeed. Use when a project gets stars but no contributions, when first-time PRs stall or get abandoned, when writing or improving CONTRIBUTING.md, when setting up a dev environment that works on the first try, or when the user asks "how do I get contributors" or…
Rules for AI implementation sessions in a wade-managed worktree. Covers worktree safety, commit conventions, syncing with main, PR summaries, and session closing. Read this at the start of every work session.
Instructions for contextual knowledge retrieval, tagging, search, and rating. Referenced by plan-session, implementation-session, and review-pr-comments-session skills.
Create one or more tasks via wade task create — for a single bug/feature OR a full plan/PRD breakdown. This is the STANDALONE task-creation workflow, used whenever the user directly asks to create a task/issue outside a wade plan session. Assesses scope, proposes a single- or multi-issue breakdown with reasoning, gets…
Daily backup of Hermes config, skills, memory, and settings to a private GitHub repo. Pure shell script, no LLM overhead. Includes cache/strip logic for minimal repo size, secret templating, and a public-repo safety check.
C# coding standards and conventions including naming, formatting, and best practices. Use when working with .cs files, writing C# code, or when the user asks about C# naming conventions, code structure, XML documentation, or .NET development patterns.
.NET coding standards and conventions including project structure, dependency injection, and best practices. Use when working with .NET projects, ASP.NET Core, or when the user asks about .NET architecture, dependency injection, async patterns, or project organization.
Standards for Nuxt.js 3 development with auto-imports, file-based routing, and SSR/SSG capabilities. Use when working with Nuxt projects, pages/, layouts/, composables/ directories, or when the user asks about Nuxt-specific patterns, server-side rendering, or Nuxt configuration.
Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf…
Use when triaging GitHub issues or pull requests - categorizing, labeling, organizing open items, validating if issues are still relevant, and reviewing/merging PRs. Handles taxonomy discovery, label creation, bulk tagging, issue staleness checks, and full PR review + merge workflows.
Scans staged and unstaged changes for sensitive data, then writes a concise commit message and commits locally. Use when the user wants to commit current work safely.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Safe git operations including commits, branches, merges, worktrees, and conflict resolution. Use when user wants to commit and push changes, manage branches, resolve conflicts, or create isolated workspaces. Activates when user says "commit", "push", "merge", "branch", "pull", "rebase", "worktree", "conflict", or…
Use when resolving unresolved PR or MR review comments, working through reviewer feedback, or addressing code review threads on GitHub, GitLab, Bitbucket Cloud, or Azure DevOps repositories.
A research-before-coding workflow for finding and comparing existing open-source projects on GitHub. It checks project details, README files, and licenses before recommending a shortlist.
Use this skill to commit changes already sitting in the working tree of the current Git repository. Inspect the tree, stage only what the user named, write one Conventional Commits message, stop. One repository per run, one commit per run.
Use this skill to submit the commits on the current branch as one pull request against a GitHub repository. Push the branch, open the PR with an imperative title and a body that names what changed and why, and post a follow-up ping only when CODEOWNERS resolves to one person. One branch per run, one pull request per…