github-workflows
Diagnose, fix, and optimize GitHub Actions workflows for Rust projects. Use when setting up CI/CD, troubleshooting workflow failures, optimizing build times, or ensuring best practices.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Diagnose, fix, and optimize GitHub Actions workflows for Rust projects. Use when setting up CI/CD, troubleshooting workflow failures, optimizing build times, or ensuring best practices.
Create implementation plans with requirements, design, and tasks. Use when planning new features or components. Generates three files with approval gates at each phase.
Commit message standards following Conventional Commits specification. Use this when writing commit messages for the Hey Jarvis project.
Guide for using GitHub MCP tools for repository operations. Use this when working with GitHub repositories, releases, tags, or branches.
Jujutsu (jj) version control commands and workflows. Use when performing version control operations, committing changes, managing branches/bookmarks, or syncing with remotes. Always use jj instead of git.
Programmatic hunk selection for jj (Jujutsu). Use when splitting commits, making partial commits, or selectively squashing changes without interactive UI.
Manage co-author attribution in commits for agentconfig.org. Use when pair programming, collaborating on changes, or when the user mentions working with another contributor.
Generate semantic commit messages following conventional commit format for agentconfig.org. Use when creating commits, reviewing staged changes, or when the user asks for help with commit messages.
Use the GitHub CLI (gh) to find and summarize relevant GitHub issues/PRs from an error message or keywords, preferring exact-phrase searches scoped to a repo and returning issue/PR numbers + URLs.
Git workflow orchestrator guiding developers through workspace setup, clean commits, and work completion across git-worktrees, git-commit, and git-finish skills
Unified documentation and context preservation: spec folder workflow (levels 1-3+), CORE + ADDENDUM template architecture (v2.0), validation, Spec Kit Memory with vector search, six-tier importance system, cons...
Self-review your own code changes using a visual diff viewer. Opens a GitHub-style web UI where you can add comments on changed lines. Comments are returned to Claude for action.
Create a GitHub pull request (PR) with proper formatting and content guidelines. Invoke this skill whenever the user wants to create, open, or submit a PR (or GitLab MR, Gerrit CR).
Browsing GitLab documentation efficiently. Use when you need to look up GitLab features, configuration, API details, or CI/CD syntax.
Implement a feature or fix based on an issue. Use when given an issue URL to work on, or when implementing changes described in a tracked issue. Supports GitHub, Linear, and GitLab.
Review a pull request when requested by a peer. Use when reviewing PRs, providing code review feedback, or analyzing proposed changes. Supports GitHub and GitLab.
Batch-process multiple issues into draft PRs using parallel worktrees. Use when implementing several related issues simultaneously, creating multiple PRs in parallel, or batch-processing a backlog.
GitLab REST and GraphQL API access via glab. Use when making API requests, querying project data, or automating GitLab operations.
Git workflow and branching best practices. Use when working with git commands, creating branches, or pushing changes.
Working with GitLab CI/CD pipelines and jobs. Use when viewing pipelines, debugging jobs, or validating CI configuration.
glab CLI basics and GitLab workflow overview. Use when working with GitLab repositories or adapting GitHub patterns to GitLab.
GitHub CLI usage and workflow patterns. Use when working with GitHub repositories, pull requests, issues, or API interactions.
Working with GitLab merge requests via glab. Use when creating, updating, reviewing, or merging MRs.
Go language coding standards, best practices, and testing patterns. Use when writing or reviewing Go code, implementing tests, or discussing Go language features.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.