5.7K skills · sorted by relevance
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
Set up Git workflows for Gitee, Coding.net, 极狐 GitLab, and CNB with platform-specific connection and authentication examples. Choose branching rules, standardize Chinese commit messages, and adapt automated testing and deployment configurations to your team's workflow.
Convert GitHub resource links into proxy URLs for cloning repositories and downloading files when access is slow. Covers release attachments, raw files, repository archives, and Gist files, with a Python helper for URL conversion.
Create concise commit messages from a code diff, a file list, or a description of changes. The skill selects one emoji that matches the change’s purpose, follows gitmoji conventions, and explains the choice without running Git commands.
Inspect GitHub and GitLab repositories, issues, and proposed code changes, then prepare small fixes with tests and review summaries. Uses existing command-line authentication and requires approval before publishing changes or modifying repository records.
Set up Kubernetes deployments with ArgoCD or Flux CD using GitOps, an approach that stores the desired system configuration in Git. Configure automatic synchronization, staged rollouts, secret management, and deployment workflows across environments or clusters.
Summarize the past 24 hours of GitHub pull requests, review requests, issues, CI runs, and merges in a daily briefing. The GitHub-style page highlights pending reviews and failed automated checks.
Prepare and submit bug reports or feature requests to GitHub, checking for duplicates and following issue templates. Reports are previewed for approval before submission, or saved locally when GitHub authentication is unavailable.
Review GitHub Actions workflows for unsafe input handling, excessive token permissions, exposed secrets, and changeable action references. Get findings grouped by issue type, with severity ratings, exact YAML locations, and concrete fixes to review.
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
The English summary is being prepared. Showing the original description.
Prepare REA changelogs and GitHub release notes from a fixed Git revision. Turn verified changes into clear user outcomes, preserve accurate contributor credit, and keep the release text aligned with Release Please, the automated release workflow.
Analyze current Git changes to choose a branch for a feature, release, or urgent fix. Create a descriptive name and switch to the new branch using Git Flow, a structured approach to managing development branches.
Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.
Guides agents to access GitHub repositories, pull requests, issues, and APIs through the authenticated gh command-line tool. Covers private repository access and recommends cloning repositories to read files locally, with commands for viewing GitHub information.
Automate DigitalOcean operations through Rube MCP, a connection for agent tools. The skill discovers supported actions and current input requirements, checks authentication, and executes the selected tools, with guidance for bulk operations and paginated results.
Automate GitHub tasks such as creating draft pull requests and inspecting automated checks. Confirms the target repository and branch before external changes, keeps actions within authorized scope, and reports the resulting URL or identifier.
Update a project's changelog using GitHub releases, git history, and code differences. Select changes that matter to users, match the existing format, and write concise entries for the requested release.
Explore how a public GitHub repository is organized using GitDiagram. Get explanations tied to component names and source paths, an interactive architecture diagram, and a narrated explainer video when one is available.
Automate DigitalOcean operations through Rube MCP, a connection for agent tools. The skill discovers supported actions and current input requirements, checks authentication, and executes the selected tools, with guidance for bulk operations and paginated results.
Investigate failed automated checks on GitHub pull requests using gh, GitHub’s command-line tool. Retrieve GitHub Actions logs, summarize failures, and propose a repair plan before implementing code changes with user approval.
Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.
Upload local screenshots, images, PDFs, archives, and videos to GitHub, then embed them in pull requests, issues, or comments. Use gh-attach to obtain attachment URLs and download existing GitHub attachments to a specified local destination.
Scan code, configuration files, and Git history for exposed AWS credentials with TruffleHog. Checks whether detected keys remain active and guides key replacement, incident investigation, and automated checks before commits and during CI/CD.
Understand a public GitHub repository through GitDiagram's architecture overview. Get an explanation of its main components, source paths, and connections, plus Mermaid diagram source and an interactive diagram for exploring the code.