3261 个 · 按相关度排序
Reduce GitHub API calls during issue monitoring by scanning basic issue details first, then fetching full descriptions and comments only for selected issues. Filters use assignees, status labels, and title patterns to narrow the list.
中文简介正在准备中。当前显示英语简介。
Manage work and personal GitHub identities in agent workflows by checking the active account and selecting credentials for each operation. It covers personal repository pushes, pull requests from forks, and separate configuration directories for account isolation.
中文简介正在准备中。当前显示英语简介。
Query GitHub issues and extract or summarize selected fields using jq, a JSON filtering tool. Inspect data structure and size before retrieving detailed results, then filter by status, author, labels, comments, or creation date.
中文简介正在准备中。当前显示英语简介。
Find and review pull requests created with GitHub Copilot using author searches, branch names, and Git history. Follow practical checks for changes and tests, and export request lists to CSV to track contributions.
中文简介正在准备中。当前显示英语简介。
Query GitHub Discussions and extract titles, authors, categories, or answer status. First inspect the data structure and size, then use jq, a JSON filtering tool, to select relevant discussions, sort updates, or count entries by category.
中文简介正在准备中。当前显示英语简介。
Retrieve labels from a GitHub repository, filter their names by partial matches, and choose page sizes and page numbers. Results arrive as JSON, including label names, colors, descriptions, and pagination details.
中文简介正在准备中。当前显示英语简介。
Review build and deployment pipelines for unsafe workflows, exposed credentials, and configuration flaws across GitHub Actions, Jenkins, GitLab CI, and Terraform state files. Use concrete evidence and false-positive checks to distinguish exploitable issues from suspicious settings.
中文简介正在准备中。当前显示英语简介。
Research a topic through five web searches, five GitHub data collections, and five X/Twitter data collections using DeepAPI. Bring coverage, relevant repositories, and social discussion together in a concise, readable Markdown report.
中文简介正在准备中。当前显示英语简介。
Handle Git and GitHub CLI commands blocked by a sandbox, an environment that restricts access. Retry only authorized commands on the host, then check authentication, repository status, or pull request details there.
中文简介正在准备中。当前显示英语简介。
Diagnose failed canary ferry runs, automated checks for failures or regressions, when invoked by CI with the required context. It gathers logs, classifies the cause, and files a GitHub issue with supporting evidence.
中文简介正在准备中。当前显示英语简介。
GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa
中文简介正在准备中。当前显示原文说明。
Use when auditing GitHub Actions workflows for script injection vulnerabilities via unsanitized context expressions. Trigger on: "github actions injection", "workflow injection", "head_ref injection", "github context injection", "pwn request", "github.head_ref", "github.event.pull_request.title", "github.event.issue.body", pull_request_target workflows, run: steps interpolating GitHub context variables, CI/CD script injection, GitHub Actions security audit.
中文简介正在准备中。当前显示原文说明。
处理OpenClaw的GitHub Secret Scanning警报，检查凭据泄露位置，遮盖正文中的机密信息，删除并重建评论，通知作者并完成警报处理。
将AI代理的工作日志整理为可附在GitHub拉取请求或议题中的记录，筛选相关内容、移除敏感信息，并支持预览及经单独授权后的发布。
收集指定会话和时间范围内分享的OpenClaw拉取请求与议题，在GitHub核实状态和依据，按影响与处理准备程度排序，并说明未能调查的范围。
按条件筛选GitHub的Issue，交给后台智能体完成修复、测试和PR创建。工作流会检查重复任务，也支持处理审核意见并定期监测新问题。
将文档、会话和项目信息分类保存到合适的位置，跨本地文件、记忆工具、知识库和数据库查重、同步与检索，并维护索引和摘要。
自动执行代码变更后的测试、类型检查和构建，建立发布前的质量检查流程。涵盖GitHub Actions配置、分阶段发布和回滚步骤，也介绍失败排查与运行提速。
检查GitHub、GitLab和Perforce变更中的评审意见、自动检查失败及说明缺漏，整理待办事项，并按请求协助修改和解决已处理的讨论。
按共同根本原因整理GitHub中积累的故障报告，建立父议题和设计文档，并协助将相关修复与防止问题复发的测试合并到一个拉取请求。
从多个服务收集网页、社交讨论、招聘信息和视频字幕等内容，覆盖16个平台。检查可用连接与登录状态，并指导选择适合目标内容的获取方式。
检查Ant Design的GitHub议题，区分缺陷与功能请求，整理回复草稿、标签调整和关闭建议，并在用户确认完整方案后执行操作。
逐条整理 GitHub 拉取请求中尚未解决的审查意见，说明问题并提出修改方案，再按用户选择修改代码、回复或跳过，处理提交及将讨论标为已解决。
按变更规模、自动检查结果、冲突及停滞情况整理GitHub待处理的拉取请求，明确审查优先级；可深入审查选定请求，起草评论并在用户批准后发布。