workflow-gerrit-fix
SkillSkillsMP
io.github.nodejs/node/workflow-gerrit-fix
Workflow for automatically fixing errors or addressing comments on a Gerrit CL requested by the user.
source
“github” 共 5,798 个结果
io.github.nodejs/node/workflow-gerrit-fix
Workflow for automatically fixing errors or addressing comments on a Gerrit CL requested by the user.
io.github.nodejs/node/v8-understanding
Guides the methodology for investigating V8 concepts, codebase structure, performance, memory, and architecture. MANDATORY to use whenever triaging bugs, investigating crashes, reading C++ files, analyzing compiler optimizations (Ignition, Maglev, TurboFan, Turboshaft), or doing static research on V8 subsystems. Essential for locating high-level design documents in the local docs/ directory before reading C++ code. Do not use for raw build commands or Git workflows.
io.github.nodejs/node/v8-workflow
Manages git task isolation and environment setup in V8. Use at the start of any new task or bug fix. Do not use for general C++ editing.
io.github.nodejs/node/trace_processor
Managing and querying Perfetto traces using the trace_processor MCP server.
io.github.nodejs/node/clangd-setup
Handles installation and configuration of clangd-mcp for V8. Use when clangd-mcp is missing or needs configuration for the current workspace. Do not use for general C++ editing.
io.github.nodejs/node/v8-security-triaging
Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
io.github.heygen-com/hyperframes/embedded-captions
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
io.github.heygen-com/hyperframes/motion-graphics
以运动本身传递信息的短设计型 motion graphic——动态字体、数字滚动、图表/数据可视化呈现、logo 片头/品牌定格、下三分之一字幕条/浮层/社媒 overlay、动画地图（区域高亮、地点连线、缩放到某地）、推文/新闻文章/标题动画、网页/UI 动画（滚动、光标、callout），或将真实图片的几何结构融入图表。通常 10 秒以内（最长约 30 秒），无旁白与真人实拍；渲染为 MP4 或透明 overlay。更长的/有旁白的/多场景的用 /general-video；不明确的用 /hyperframes。
io.github.heygen-com/hyperframes/hyperframes-audio
当 HyperFrames 合成中已放置的音频需要混音时使用：淡入/淡出、crossfade、轨道增益或音量、音量自动化、ducking、与旁白冲突的音乐垫（voiceover carve）、对轨道施加效果（EQ、压缩、限制、门限、饱和、延迟、混响、合唱、移相、bitcrush）、在轨道音量或任意效果参数上绘制自动化包络，或用一个 submix 总线承载链路、用 `<hf-audio-group>` 让一个推子和一个自动化时钟同时控制多条轨道。不用于音频获取或生成——找 BGM、音效或制作旁白属于 `/media-use`。不用于片段时序或轨道布局，那属于 `/hyperframes-core`。
io.github.heygen-com/hyperframes/hyperframes-keyframes
当 HyperFrames 合成需要推近、拉出、缩放、改构图、Ken Burns 效果、运镜、视觉匹配/甩镜交接，或其他 seek-safe 的 2D/3D 关键帧时使用；也用于 GSAP、CSS keyframes、Anime.js、WAAPI、FLIP、路径、遮罩、SVG morph/draw、文字拖尾、3D 纵深，或 `hyperframes keyframes` 诊断。不要用于宽泛的场景策略、品牌设计、素材获取、字幕或一般视频规划。
io.github.pranshuparmar/witr/witr
Explains why a process is running and what started it, using the witr CLI. Use when a port is already in use (EADDRINUSE), a dev server or other process was left running, an unknown or stuck process needs explaining, or you need to know which service, container, shell, supervisor or scheduled job started a process, holds a port or holds a file lock. Use it instead of chaining lsof, ps, ss, netstat and docker ps.
io.github.heygen-com/hyperframes/pr-to-video
把 GitHub pull request（PR 链接、owner/repo#N，或在已检出仓库中指“这个 PR”）做成代码变更讲解视频——基于 diff、commits 与文件构建的更新日志、功能揭示、修复或重构讲解：输入是代码变更而不是网站。不是产品宣传片（/product-launch-video），也不是无 PR 的主题讲解（/faceless-explainer）。不确定时先用 /hyperframes。
io.github.docling-project/docling/docling
用 Docling 理解任意受支持格式文档的内容——PDF（原生数字或扫描件）、DOCX、PPTX、XLSX、HTML、Markdown、AsciiDoc、CSV、图片、音频与 XML——把它们统一转换为 DoclingDocument（Markdown 或结构化 JSON）。当你需要读取、解析、转换、提取或切分无法直接阅读的文档时使用，例如“这份 PDF 里有什么”“转成 markdown”“提取表格”“为 RAG 切块”“读这份扫描文档”“解析这个 DOCX/PPTX”。涵盖 docling CLI、Python SDK（DocumentConverter 与 PipelineOptions）、远程 Service Client（自托管或托管的 docling-serve），以及用于最小依赖体积的 docling-slim install extras。
io.github.ossrs/srs/internal-codemap-for-srs
把 SRS 与 Oryx 的代码任务路由到最小相关的可信代码库地图与验证指引。只要支持、开发、调试、评审或维护工作需要定位、选择、阅读、修改、测试或验证 SRS/Oryx 代码时使用。覆盖第一代 C++ 源站与边缘媒体服务器及其 State Threads 依赖、下一代 Go 服务器、浏览器推流与播放、SRS Docker 镜像工具链、SRS 测试，以及 Oryx 的 Go 后端、React 控制台、一体化运行时、打包、安装器、发布与测试。作为父级支持与发展技能的代码导航依赖；面向用户的工作流程与结果仍由父技能负责。
io.github.ossrs/srs/srs-develop
SRS 与 Oryx 代码库以及 SRS Docker 镜像工具链的开发、修改、调试、评审、维护与讲解。用于对下一代 SRS Go 代理、SRS 浏览器播放器、ossrs/dev-docker 镜像，以及 Oryx 的 Go 后端、React 控制台、一体化运行时、打包、安装器、发布与测试做计划性改动；也包括缺陷维护、issue 与 PR 分诊、PR 评审以及 Learn Code 提问。C++ 版 SRS 服务器已进入维护模式，基于 Go 的新版源站与边缘节点的规划性开发尚不支持。不适用于终端用户支持、使用提问或配置咨询——这些请使用 srs-support。
io.github.NVIDIA/OpenShell/debug-openshell-cluster
诊断 OpenShell gateway 部署为何不健康、不可达或无法创建 sandbox。适用于 gateway 健康失败、Docker/Podman 运行时问题、Helm 失败、Kubernetes 调度、TLS 或认证、gateway 拦截器、supervisor middleware 启动或运行时失败、外部 compute-driver socket、VM 驱动、sandbox 启动等问题。触发词：debug gateway、gateway failing、deployment failing、helm install failing、cluster health、gateway health、gateway not starting、health check failed、sandbox pending、docker driver、podman driver、kubernetes driver、external driver、compute driver socket、gateway interceptor、supervisor middleware、middleware failed、vm driver。
io.github.pytorch/pytorch/scrub-issue
获取、分析、复现并精简 GitHub issue 的复现步骤。仅在用户要求验证某个 GitHub issue 是否可复现、精简其复现用例、分析 bug 报告，或为可复现性对 issue 做审查/分诊时使用。不适用于没有对应 GitHub issue 的独立复现请求。
io.github.pytorch/pytorch/ci-metrics
查询 PyTorch CI、GitHub Actions、HUD、Grafana 与基础设施指标。当用户询问 CI 耗时、任务失败、排队时长、工作流趋势、runner 健康度、看板数据或 PyTorch 基础设施指标时使用。
io.github.pytorch/pytorch/fix-issue
复现并定位 PyTorch GitHub issue 报告的 bug，在本地工作区实现修复。当用户要求修复 PyTorch GitHub issue 时使用。
io.github.pytorch/pytorch/triaging-issues
对 GitHub issue 进行分诊：路由到值班团队、打标签并关闭咨询类问题。在处理新的 PyTorch issue 或被要求分诊 issue 时使用。
io.github.pytorch/pytorch/pt2-bug-basher
调试 PyTorch 2 编译器栈故障，包括 Dynamo 图断裂、Inductor 代码生成错误、AOTAutograd 崩溃与精度不一致。在遇到 torch.compile 错误、BackendCompilerFailed 异常、重编译问题、Triton kernel 失败、FX 图问题，或用户提到调试 PT2、Dynamo、Inductor 或编译模型问题时使用。
io.github.TriliumNext/Trilium/maintaining-docker-hub
Use when working on Trilium's published Docker images on Docker Hub or GHCR rather than on the Dockerfiles — "how many pulls does the image get?", "why is the Docker Hub repository so big?", "clean up old tags", "delete untagged images", "which tags do we publish?", the legacy repositories (triliumnext/notes, zadam/trilium) and their mirroring, the main-docker.yml copy-to-Docker-Hub step, mirror-legacy-docker.yml, Docker Hub categories, stars or the overview. Includes hub.mjs (stats, tag listing/deletion, the manifest inventory and a safe untagged-image purge, all dry-run by default) and the storage model that decides how a cleanup works. Do NOT use for building or running the image locally (see the Developer Guide's Docker page).
io.github.QwikDev/qwik/qwik-core-development
用于修改或审阅 packages/qwik 下的 Qwik 核心包代码，尤其是响应式原语、信号、VNode、cursor 行为、QRL，以及面向 optimizer 的运行时行为，或 Qwik 核心测试。
io.github.The-Vibe-Company/quivr/mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.