New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Managing Git Workflow

by hashintel in hashintel/hash

Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics.

AGPL-3.0Auto-check passedDevelopment

Install Managing Git Workflow

skills CLI
$ npx skills add hashintel/hash --skill managing-git-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashintel/hash managing-git-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/managing-git-workflow .claude/skills/managing-git-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managing-git-workflow
GitHub stars
1.7k
Token cost
~1.2k tokens
SKILL.md length
514 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics.

  • Naming a branch
  • SKILL.md covers Contributing, Reviewing Pull Requests and Merge Queue
  • Calls gh and cargo
  • Reviewing a pull request

What it does

Managing Git Workflow is an agent skill from hashintel/hash. Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics. Use when naming a branch, opening or reviewing a pull request, interpreting its checks, or diagnosing a merge-queue ejection.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Pull requests. It works with Git, Linear and GitHub. The repository describes itself as: 🚀 The open-source, multi-tenant platform for self-building knowledge graphs and simulation. The licence is AGPL-3.0.

When your agent uses it

  • Naming a branch
  • Reviewing a pull request
  • Interpreting its checks
  • Diagnosing a merge-queue ejection

Example prompts

  • “/managing-git-workflow”

What it can do on your machine

Read from SKILL.md and the folder at commit e189ab2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Git Workflow loads about 1.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 514 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashintel/hash at commit e189ab2, republished under its AGPL-3.0 licence (© hashintel). 514 words, ~1,183 tokens.

Download SKILL.mdSave it as .claude/skills/managing-git-workflow/SKILL.md (or your agent's skills folder).
name
managing-git-workflow
description
Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics. Use when naming a branch, opening or reviewing a pull request, interpreting its checks, or diagnosing a merge-queue ejection.
license
AGPL-3.0

Managing Git Workflow

Use ordinary Git and GitHub as the public baseline. No particular Git client or access to HASH's Linear workspace is required to contribute.

Contributing

Treat .github/CONTRIBUTING.md as the source of truth for contribution policy and .github/pull_request_template.md as the source of truth for PR content.

Working From a HASH Linear Issue

When the work has an associated HASH Linear issue, preserve traceability in the branch and pull request:

  • Name the branch <shortname>/<team-key>-xxxx-description, with the Linear identifier in lowercase; for example, ln/fe-1437-hash-monorepo-import or ln/h-6786-agent-guidance-layout.
  • Title the PR {ISSUE-ID}: Description, preserving the identifier's uppercase form; for example, H-6786: Stop copying HASH agent guidance into unused tool folders.
  • Link the Linear issue in the PR's related links and mark it _(internal)_ when it is not publicly accessible.

Current HASH Linear identifiers commonly use FE-, SRE-, BE-, or H- prefixes.

Contributing Without a HASH Linear Issue

Contributors without access to HASH's Linear workspace do not need a Linear identifier. Use a descriptive branch name and PR title, and link the relevant public issue or discussion for significant work. Minor documentation fixes may go straight to a PR as described in the contributing guide.

In every case, keep the PR description self-contained so contributors and reviewers without access to internal systems can understand the change. Fill every applicable section of the PR template and say when a section is unknown or inapplicable.

Reviewing Pull Requests

Gather the public review record and the complete diff:

bash
gh pr view <PR_NUMBER> --comments
gh pr diff <PR_NUMBER>
gh api \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  /repos/hashintel/hash/pulls/<PR_NUMBER>/comments

Use the PR description and linked public issue or discussion as the public review contract. If the PR references a HASH Linear issue and the reviewer has access, fetch it and use its requirements as an additional review baseline. Treat inaccessible internal links as supplemental provenance, not as requirements the public artifact may omit.

  • Review the full diff without truncating it.
  • Identify blocking findings separately from optional suggestions.
  • Give precise file and line locations.
  • Leave resolution of a review thread to the reviewer who opened it, as specified in the contributing guide.
Show full SKILL.md (181 more words)Show less

Merge Queue

HASH merges through GitHub's merge queue. This section applies to maintainers and to diagnosing queue checks; contributors do not need merge-queue access.

Verify an Enqueue

The PR's auto_merge field remains null after a successful enqueue, so it is not evidence either way. Verify with either:

  • a recent added_to_merge_queue event in GET /repos/hashintel/hash/issues/<NUMBER>/timeline
  • fresh merge_group workflow runs on a gh-readonly-queue/<base>/pr-<NUMBER>-<sha> ref
Diagnose an Ejection

An ejection can be another PR's fault or an infrastructure failure:

  • The gh-readonly-queue/... ref names every PR in the batch. If only one PR is named, it was not batched with another.
  • Compare the failing step against the same step on the identical head in the PR-level run before attributing it to the diff.
  • Check whether a changed file is listed in turbo.json under globalDependencies; a global invalidation can run unrelated package checks and expose unrelated failures.

The PR runs cargo clippy --all-features; the merge queue runs cargo hack --optional-deps --feature-powerset clippy, selected through GITHUB_EVENT_NAME in .justfile. Queue lint can therefore surface feature-conditional problems that PR lint did not run, including the unused-dependency gate in .github/workflows/lint.yml.

© hashintel, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/managing-git-workflow of hashintel/hash.

Open the folder on GitHubat commit e189ab2

Compare with similar skills

Managing Git Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing Git Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managing Git Workflow this skillhashintel/hash1.7k—~1.2kAutomated safety check: PassAGPL-3.0
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Create Pull Request with Work Item IDmakeplane/plane60k—~824Automated safety check: PassAGPL-3.0

Similar skills

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    60k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

More from hashintel/hash

All 17 skills in this repo

  • Documenting Rust Code

    hashintel/hash

    Rust documentation practices for HASH codebase. An agent skill from hashintel/hash.

    1.7k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Handling Rust Errors

    hashintel/hash

    HASH error handling patterns using error-stack crate. An agent skill from hashintel/hash.

    1.7k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Managing Cargo Dependencies

    hashintel/hash

    Cargo.toml dependency management patterns for HASH workspace.

    1.7k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Testing Hashql

    hashintel/hash

    HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests.

    1.7k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Writing Hashql Diagnostics

    hashintel/hash

    HashQL diagnostic writing patterns using hashql-diagnostics crate.

    1.7k GitHub stars~724 tokensUpdated today
    Auto-check passed

  • Writing Hashql Jexpr

    hashintel/hash

    HashQL J-Expr syntax for writing queries. An agent skill from hashintel/hash.

    1.7k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Managing Git Workflow

What does Managing Git Workflow do?

Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics. Managing Git Workflow is an agent skill from hashintel/hash. Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics.

When should I use Managing Git Workflow?

Managing Git Workflow fits situations like: naming a branch; reviewing a pull request; interpreting its checks; diagnosing a merge-queue ejection.

How do I install Managing Git Workflow in Claude Code?

Run `npx skills add hashintel/hash --skill managing-git-workflow -a claude-code`. Or copy the skill folder (.agents/skills/managing-git-workflow in hashintel/hash) into .claude/skills/managing-git-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Managing Git Workflow in Codex?

Run `npx skills add hashintel/hash --skill managing-git-workflow -a codex`. Or copy the skill folder (.agents/skills/managing-git-workflow in hashintel/hash) into .agents/skills/managing-git-workflow in your project. Codex loads it when a task matches its description.

Can I use Managing Git Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashintel/hash --skill managing-git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-git-workflow, .gemini/skills/managing-git-workflow, .github/skills/managing-git-workflow and .opencode/skills/managing-git-workflow in your project.

What does Managing Git Workflow need to run?

Going by SKILL.md and its folder, Managing Git Workflow needs the command-line tools its instructions call (gh and cargo).

Does Managing Git Workflow access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Managing Git Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managing Git Workflow use?

Managing Git Workflow is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing Git Workflow use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Managing Git Workflow?

Skills that share tags, products or a category with Managing Git Workflow: Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Git Workflow?

hashintel (a GitHub organization) maintains it in hashintel/hash, which has 1,668 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: hashintel/hash on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.