Deploy TwinMind integrations to production environments. Use when deploying to cloud platforms, configuring production infrastructure, or setting up deployment automation. Trigger with phrases like "deploy twinmind", "twinmind production deploy", "twinmind cloud deployment", "twinmind infrastructure".
Set up TwinMind across multiple environments (dev, staging, production). Use when configuring environment-specific settings, managing multiple API keys, or implementing environment promotion workflows. Trigger with phrases like "twinmind environments", "twinmind multi-env", "twinmind staging setup", "twinmind dev vs prod".
Complete production deployment checklist for TwinMind integrations. Use when preparing to deploy, auditing production readiness, or ensuring best practices are followed. Trigger with phrases like "twinmind production", "deploy twinmind", "twinmind go-live checklist", "twinmind production ready".
Writes an implementation plan with small steps, exact files to touch, and verification commands. Use before making non-trivial changes.
Finalizes work: runs verification, summarizes changes, notes follow-ups, and ensures repo hygiene. Use at the end of an implementation or debugging session.
Shared LibreQoS workflow for node_manager frontend work. Use when changing src/rust/lqosd/src/node_manager/js_build/**, static2/**, esbuild.sh, copy_files.sh, dev_build.sh, static_pages.rs, or the overall Bootstrap 5 and FontAwesome-based UI.
Shared LibreQoS Rust workflow for repo contributors. Use when changing Rust under src/rust, validating Rust crates, deciding between workspace commands and --manifest-path, or applying LibreQoS-specific Rust conventions and verification steps.
涉及git worktree的操作优先使用这个skill。管理 Git bare 仓库和多个并行 worktree 的开发环境。支持初始化 bare 仓库结构、自动生成分支名并创建 feature worktree。
Create GitHub issues with consistent title casing, type prefixes, and body structure for the videojs/v10 repo. Use when filing bugs, requesting features, or creating any ticket/issue. Triggers: "create issue", "new issue", "file issue", "open issue", "file bug", "request feature", "create ticket", "new ticket", "file ticket", "open ticket".
Explains code for experienced engineers. Covers what changed, why it works, non-obvious decisions, gotchas, and data/control flow. Defaults to git diff vs main; accepts an optional file or path argument.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Bump the project version number across manifest.json and package.json, then create a git tag. Use when the user says "bump version", "release", "new version", "version bump", or asks to increment the version number.
Prevent predictable Shopify CLI PR CI failures before push or submit. Use when users: (1) ask what to run before pushing, submitting, restacking, opening, or updating a PR, (2) ask which generated files to commit or stage, (3) want to validate a branch against GitHub Actions, or (4) want to avoid CI churn after command, docs, workflow, schema, or test changes. At PR time, default to suggesting the minimal pre-submit checks rather than running a full local workflow automatically.
Isolate a subset of changes from a dirty local worktree (usually on main) into a clean feature branch, then commit, push, and open a PR. Use when the user asks to "branch out", "isolate my changes", "move this work to a new branch", or create a clean PR from only selected files/hunks.
Check if uncommitted changes are important/risky/breaking to require a review before merge/production release.
Safely sync local commits with remote by rebasing onto origin/main and then push, following a GitHub Desktop-style flow. Use when asked to push/sync a branch, reconcile local and remote state, resolve rebase conflicts, run targeted tests or typechecks, and push only if checks pass.
Git operations: commits, branches, PRs, and conflict resolution
Interact with GitHub using the `gh` CLI. Use when users ask about pull requests, issues, CI/CD status, workflow runs, repository information, or want to create, review, or merge PRs. Covers `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, pull requests, actions, checks, releases, and advanced queries. Triggers on mentions of GitHub, pull request, PR, issue, workflow, actions, checks, or merge.
Workspace file management, git versioning, directory conventions, and CLI execution safety rules for the Research-Claw workspace.
Guides creation of kcli plan files for deploying VMs, networks, and infrastructure. Use when writing YAML plans with Jinja2 templating or debugging plan execution issues.
