TypeScript 安全研究须知
SkillSkillsMP
io.github.microsoft/typescript/security-report-check
你在对本仓库做安全研究吗？本文说明仓库能提供和不能提供哪些保障。在上报安全问题或开展安全研究之前请先阅读。
source
“3” 共 2,726 个结果
io.github.microsoft/typescript/security-report-check
你在对本仓库做安全研究吗？本文说明仓库能提供和不能提供哪些保障。在上报安全问题或开展安全研究之前请先阅读。
io.github.nodejs/node/v8-regression-testing
Use this skill when designing, writing, or minimizing regression tests (e.g., mjsunit) for V8 bug fixes
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.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.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.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.
io.github.microsoft/vscode/policy-and-managed-settings
在新增、修改或评审任何 Copilot、agent、LLM、AI、工具、权限、沙箱、MCP、模型、遥测、功能门禁、设置、配置或企业级管控时使用——尤其是组织或管理员可能需要管理的内容。从这里开始判断它应落在运行时管理设置、类型化 SDK 契约、VS Code configuration policy、扩展策略，还是拆分的实现中。每个新的 Copilot/agent/LLM 管控项，以及任何新增 policy: 字段的改动都要执行。
io.github.deepseek-ai/deepseek-harness/cordis-composition-reference
Use when writing or reading a Cordis bundle patch or agent preset for this harness and you need the Loader YAML dialect (insert, override by id, group, disabled, isolate, !!js) or the list of installable Harness plugin packages and what each provides.
io.github.RSSNext/Folo/mobile-release
在从 dev 分支准备移动端发布、决定改动经应用商店还是 OTA 管线交付，并向 mobile-main 创建发布 PR 时使用。
io.github.RSSNext/Folo/release-promo
Announcement kit for a Folo release - the X post with the highlights, its reply with the release links, a one-sentence quote line for the second account, and a 1080p promo video rendered from real app captures. The desktop and mobile release skills end with it; also use it when the user asks for promo material for a release.
io.github.RSSNext/Folo/release-promo
Announcement kit for a Folo release - the X post with the highlights, its reply with the release links, a one-sentence quote line for the second account, and a 1080p promo video rendered from real app captures. The desktop and mobile release skills end with it; also use it when the user asks for promo material for a release.
io.github.RSSNext/Folo/mobile-release
Full Folo mobile release from dev to the stores. Decides between a store release and an OTA-only release, drafts the changelog, bumps the version and opens the release PR to mobile-main, verifies the PR's CI-built Android package and the iOS build on a simulator along with every change in the release, merges the PR, watches the build or OTA workflows, publishes the GitHub release, submits the iOS build for App Store review and the Android build for Google Play review, and drafts the announcement post and promo video. Use when the user asks to release, ship or publish the mobile app.
io.github.microsoft/vscode/ci-artifact-testing
Use when validating an upstream pull request or dependency fix against VS Code tests using GitHub Actions CI build artifacts instead of building locally. Covers finding compatible binaries, verifying PR and merge-commit provenance, selecting a candidate runtime or build, comparing unchanged regression tests, and restoring the baseline.