Skip to content
TrustedSkillsbeta
Back to all skills

Git Workflow

Checked
mindrally·vlatest·backend·Apache-2.0

Automates Git workflows, merging pull requests & resolving conflicts directly within your MindRally project backend.

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 mindrally/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

mindrally

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 mindrally/skills at 7682ca7771.

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

Commit
7682ca7771
Manifest
git-workflow/SKILL.md
Scanned
1 file, 164 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

The git-workflow skill enables AI agents to execute version control operations directly within a repository, managing code history and branching strategies. It automates routine tasks like committing changes, creating branches, and merging pull requests to streamline backend development pipelines.

When to use it

  • Automating the commit process after an agent generates or modifies code files.
  • Creating feature branches for isolated experimentation before integrating changes.
  • Resolving merge conflicts by executing standard Git commands to reconcile divergent histories.
  • Cleaning up local repositories by removing untracked files or resetting specific states.

Key capabilities

  • Executing core Git commands (add, commit, push, pull, branch, merge).
  • Managing repository state through file staging and history tracking.
  • Facilitating collaborative workflows via branch creation and integration.

Example prompts

  • "Create a new branch named feature/user-auth and switch to it."
  • "Stage all modified files and commit the changes with the message 'Fix login bug'."
  • "Merge the develop branch into the current branch and resolve any conflicts."

Tips & gotchas

Ensure the AI agent has read/write access to the remote repository before attempting push or merge operations. Always verify the target branch name and commit messages to prevent accidental overwrites of critical code history.