Skip to content
TrustedSkillsbeta
Back to all skills

Git Workflow

Listed
asyrafhussin·vlatest·backend·MIT

Automates common Git workflow tasks like branching, merging, and pull requests based on asyrafhussin's established practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add asyrafhussin/agent-skills --skill git-workflow -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

asyrafhussin

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 10 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: chris.beams.io, cli.github.com, commitlint.js.org, docs.github.com, git-scm.com….

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    git-scm.comundeclaredwww.conventionalcommits.orgundeclareddocs.github.comundeclarednvie.comundeclaredsemver.orgstandardschris.beams.ioundeclaredwww.atlassian.comundeclaredgoogle.github.ioproject documentationtrunkbaseddevelopment.comundeclaredcli.github.comundeclaredcommitlint.js.orgundeclaredtypicode.github.ioproject documentationsemantic-release.gitbook.ioundeclaredgithub.comsource host

    What it found (3 of 14)

    • skills/git-workflow/metadata.json:61contacts git-scm.com
      "url": "https://git-scm.com/doc",
    • skills/git-workflow/metadata.json:67contacts git-scm.com
      "url": "https://git-scm.com/book/en/v2",
    • skills/git-workflow/metadata.json:79contacts git-scm.com
      "url": "https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project",

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned asyrafhussin/agent-skills at 1aa0ff717c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1aa0ff717c
Manifest
skills/git-workflow/SKILL.md
Scanned
37 files, 4,371 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidelines and automates tasks related to Git workflow management, based on established best practices. It covers commit message conventions, branching strategies, pull request workflows, and history management. The goal is to help maintain a clean and useful Git repository history by enforcing specific rules and providing references for common scenarios.

When to use it

  • When writing commit messages to ensure they adhere to conventional standards.
  • During the creation of new branches, ensuring consistent naming and following feature branch workflows.
  • To review pull requests and verify adherence to established practices like small PR sizes and CI pass requirements.
  • For maintaining a clean Git history through techniques like rebasing and avoiding force pushes.
  • When deciding between different branching strategies (GitFlow, GitHub Flow, Trunk-Based).

Key capabilities

  • Commit Message Conventions: Enforces guidelines for commit message formatting, including using imperative present tense, adding bodies for complex changes, and referencing issues/tickets.
  • Branching Strategy Guidance: Provides recommendations for branch naming, feature branches, protecting the main branch, and managing release branches.
  • Pull Request Workflow: Offers advice on creating small, well-described pull requests with appropriate reviewers and ensuring CI passes.
  • History Management Techniques: Covers topics like rebasing versus merging and avoiding force pushes to shared branches.

Example prompts

  • "What are the guidelines for writing a commit message?"
  • "How should I name a feature branch?"
  • "What's the recommended workflow for pull requests?"
  • "Explain GitFlow vs GitHub Flow."

Tips & gotchas

  • This skill provides guidelines and references, it doesn’t automatically enforce all rules. You may need to configure additional tools (like Husky + commitlint) as suggested in the "Commit Messages" section for full enforcement.
  • The skill covers a wide range of Git workflows; prioritize based on your team's needs and existing practices.