Skip to content
TrustedSkillsbeta
Back to all skills

Git Pr Workflows Onboard

Listed
sickn33·vlatest·backend·MIT

Automates Git pull request workflows, streamlining code reviews and merging based on predefined rules and best practices.

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 sickn33/agentic-awesome-skills --skill git-pr-workflows-onboard -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

sickn33

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.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Scanned
0 files
Copies in repo
3 — all of them scanned
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 automates the onboarding of new contributors into a Git repository by setting up personalized workflows. It configures branch protection rules, defines required review steps, and establishes automated CI/CD pipelines tailored to the new user's role.

When to use it

  • New Team Member Integration: Automatically configure a developer's environment and access rights upon their first commit.
  • Enforcing Code Quality Standards: Ensure all pull requests undergo mandatory security scans and code reviews before merging.
  • Role-Based Access Control: Restrict write permissions for junior developers while granting full control to senior engineers.
  • Streamlining Project Setup: Initialize a new repository with pre-defined workflows, issue templates, and contribution guidelines instantly.

Key capabilities

  • Configures branch protection rules (e.g., requiring pull requests, status checks).
  • Sets up automated CI/CD pipelines for testing and deployment.
  • Defines custom review requirements based on file changes or author roles.
  • Integrates with existing Git hosting platforms like GitHub or GitLab.

Example prompts

  • "Onboard a new backend developer to the project by setting up their branch protection rules and required status checks."
  • "Create a pull request workflow that mandates two approvals and runs security scans for all changes in the src directory."
  • "Initialize a new repository with automated testing pipelines and restrict direct pushes to the main branch."

Tips & gotchas

Ensure your Git hosting platform supports the specific workflow features you intend to configure, as some advanced rules may require premium plans. Always test the configured workflows in a staging environment before applying them to production branches to avoid blocking legitimate contributions.