5.8K skills · sorted by relevance
Analyze Git changes and generate Conventional Commits messages, a standard format that labels each change by type. Suggest separate commits for unrelated work, then stage files and commit as needed, using Git alone.
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.
Monitor RSS feeds, JSON APIs, and GitHub activity at regular intervals. Included scripts track previously seen item IDs and output only new entries, letting an agent report updates while staying silent when nothing has changed.
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.
Manage Git user settings and authentication for a specific workspace. Set configuration values, register HTTPS access tokens, and import SSH keys, with options to list or remove credentials without exposing stored tokens or private keys in listings.
Inspects GitHub repositories, pull requests, issues, reviews, and automated Actions runs through the connected iPolloWork service. Combines remote information with the local checkout, summarizes relevant evidence, and routes review fixes, CI investigation, or publishing to specialist workflows.
Use Git changes to generate Conventional Commits messages, a format that labels each change by type, and create commits. The skill suggests splitting unrelated changes and supports explicit scope, type, sign-off, and amendments to the previous commit.
Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.
The English summary is being prepared. Showing the original description.
Rebuild OpenClaw release changelogs from Git history, the recorded code changes. Group changes by user impact, preserve issue and pull request references and contributor credits, and verify the notes against the release history and published GitHub release text.
Triage GitHub issues and pull requests, classify their next steps, and connect active work to Linear. Keeps public updates in GitHub and internal ownership and priorities in Linear, with a clear recommendation for the next action.
Guide Git operations with explicit authorization for history changes and destructive actions. It defines recovery snapshots before discarding work, careful handling of locks and index corruption, and checks that keep unexplained changes out of commits.
Search and work with GitHub repositories through GitHub’s official MCP server, which connects agents to available tools. The skill guides account authorization, repository access selection, and tool use, with separate controls for reading and making changes.
Refresh the GitHub star count displayed on Remotion’s website. It checks GitHub, rounds the number down to the nearest thousand, updates three components, and commits and pushes the changes to main.
Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.
Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.
Build GitLab workflows that automate building, testing, and deployment. The skill covers pipeline stages, dependency caching, runners that execute jobs, and manual approval before production deployment, with examples for Docker, Kubernetes, and Terraform.
Route Git tasks to a dedicated agent to organize commits, branches, and project history. It supports focused commits, repository commit style detection, and interactive rebasing, which lets you reorganize existing commits.
Inspect project files to identify languages and build tools, then generate starter GitHub Actions or GitLab CI workflows. Set up automated checks, caching, and deployment stages that reflect the project’s commands and target environments.
Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.
Investigate failing GitHub Actions checks on a pull request using the GitHub CLI. The skill gathers logs, summarizes failures, and proposes a fix plan, then implements changes only after explicit approval and reports changes and tests.
Emulated GitHub REST API for local development and testing. Use when the user needs to interact with GitHub API endpoints locally, test GitHub integrations, emulate repos/issues/PRs, set up GitHub OAuth flows, configure GitHub Apps, test webhooks, or work with actions/checks without hitting the real GitHub API. Triggers include "GitHub API", "emulate GitHub", "mock GitHub", "test GitHub OAuth", "GitHub App JWT", "local GitHub", or any task requiring a local GitHub API.
The English summary is being prepared. Showing the original description.
Establish a Git workflow for team development, from choosing branches for separate changes to writing clear commits and pull requests. Includes history cleanup, merge versus rebase decisions, conflict resolution, and release tagging.