搜索「Pipeline」的结果

io.github.microsoft/PowerToys/ui-tests-local-vm

Run PowerToys UITest.Next suites in persistent Hyper-V VMs over PowerShell Direct. Validate full default and constrained suites on Windows 10 and Windows 11, plus applicable ARM64 guests, then automatically hand implementation tasks to ui-tests-pipeline-ci for commit/push and CI validation. Local green is not end-to-end completion. Use for agentic UI-test iteration, reusable standard-user desktops, payload staging, evidence export, VM customization, clean baselines, or hosts without nested virtualization. Keywords: Hyper-V, local VM, virtual machine, PowerShell Direct, Copy-VMFile, VMBus, checkpoint, unattend, autounattend, ISO, Windows 10 LTSC, Windows 11, ARM64, Windows on ARM, UI tests, UITest.Next, winappcli, TRX, CI handoff.

发布流程

io.github.slopus/happy/release

面向 CLI、移动端、Web 与后端的发布流水线。引导版本递增、构建、测试、发布与部署。以 Claude Code 原生体验取代旧的交互式 release-it 流程。当用户输入 /release，或要求发布、推送、部署或交付任意组件时使用。

Sandbox 性能基准（A/B）

io.github.vercel/next.js/sandbox-bench

在 Vercel Sandbox VM 上以配对 A/B 统计对 React 或 Next.js 改动做基准测试：react PR/commit 对比 base，或 Next.js PR/commit 对比 base，经由 bench/render-pipeline 应用做端到端测量（rps、延迟、p95；如 Next 侧采集则含 TTFB、RSS 及 document/Flight 字节），React 改动还会走 react 仓库的 flight-ssr-bench fixture（Node 与 Edge web-streams 路径、Fizz 与 Flight+Fizz）。当用户要求 bench、性能测试或 A/B 一个 React PR、react-server-dom / Flight / vendored React 改动、或 Next.js PR（如“这个 PR 更快吗”“会不会让 RSC 退化”“量化 <commit> 的性能影响”）时即可使用——凡是量化两个版本间服务端性能差异的请求都属于此场景。远端运行（不占用笔记本），测量前先过正确性闸门，并给出 boot 级别的置信区间。

lobe-design

io.github.lobehub/lobehub/lobe-design

Single entry for LobeHub UI design work. Routes any instruction — macro ("重做这个后台", "整体打磨一下"), medium ("把列表页的交互和空态补齐") or fine ("这个按钮颜色不对", "修 K-07") — into a business-first, layered pipeline of focused stages: 00 brief → 05 init → 10 decode → 20 direction → 30 structure → 40 flow → 50 visual → 60 system → 70 detail → 75 copy → 80 review. Covers seven scenarios: 0→1 visual pages (landing / portfolio / campaign), polishing existing product UI, admin consoles / dashboards / forms / workflows, design-system unification, screenshot restoration, pre-launch audit, and project bootstrap (AGENTS.md). Grounded in classic analysis models (double diamond, Gestalt, Nielsen heuristics, Kano, peak-end, Fogg, journey map, cognitive load) and in a layered component boundary: take atoms from @lobehub/ui, build business composites yourself. Built on @lobehub/ui, @lobehub/ui/form, @lobehub/ui/pro-table, cssVar tokens, @lobehub/charts / icons / fluent-emoji / streamdown, with runnable lint, route, refs and bootstrap checks; in-pr

animation-performance

io.github.emilkowalski/skills/animation-performance

Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Covers the layout/paint/composite pipeline, cheaper property swaps, CSS vs WAAPI vs requestAnimationFrame, Framer Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, and when `will-change` actually helps. Use when an animation is janky, choppy, stutters, or drops frames; when choosing which property to animate; when deciding between CSS and JS animation on performance grounds; or when reaching for `will-change` or GPU layers. For choosing easing, duration, or whether to animate at all use animate; for reviewing motion as a whole use review-animations.

brownfield-retrospective

io.github.affaan-m/ECC/brownfield-retrospective

Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.

revops（收入运营）

io.github.coreyhaines31/marketingskills/revops

当用户需要收入运营、线索生命周期管理或市场到销售的交接流程支持时使用。用户提到 RevOps、revenue operations、线索评分、线索路由、MQL、SQL、pipeline stages、deal desk、CRM 自动化、marketing-to-sales handoff、数据清洗、线索没有流转到销售、pipeline 管理、线索资格判定，或“市场何时该交接给销售”等场景时也适用。凡涉及连接市场与收入的系统和流程均可使用。冷邮件触达见 cold-email，邮件序列营销见 emails，定价决策见 pricing。

PowerToys UI 测试迁移

io.github.microsoft/PowerToys/ui-tests-migration

将 PowerToys UI 测试从 WinAppDriver/Selenium 迁移并稳定到 Microsoft.PowerToys.UITest.Next 与 winappcli。适用于移植、新建 UITest 工程、CI flaky 测试、本地 Hyper-V 虚拟机持续验证、可重置的干净基线运行、Settings IPC 鉴权/测试签名、Explorer/Shell 选择、预览 handler、缩略图提供程序、快捷键激活、有状态进程生命周期、WinUI/WebView 合成视觉基线，以及跨窗口/前台失焦问题。涵盖 API、脚手架、测试设计、诊断、agent 化执行与 CI 加固。关键词：UI test、UITestAutomation.Next、winappcli、WinAppDriver、Selenium、Settings IPC、Authenticode、local VM、Hyper-V、checkpoint、flaky、CI stability、WebView2。

workflow-create

io.github.ruvnet/ruflo/workflow-create

Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)