Skip to content
TrustedSkillsbeta
Back to all skills

Fastdeploy Pull Request

Checked
pfcclab·vlatest·backend

Automates creating pull requests in FastDeploy, streamlining code merging and accelerating development workflows by eliminating manual steps.

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 pfcclab/paddle-skills --skill fastdeploy-pull-request -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

pfcclab

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 pfcclab/paddle-skills at 309bb22fdb.

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

Scanned
1 file, 134 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 automates the process of creating and submitting pull requests to a specified repository. It handles generating diffs, formatting commit messages according to conventions, and pushing changes to remote branches. The primary goal is streamlining code contribution workflows within PaddleSkills projects.

When to use it

  • You need to contribute code changes back to a PaddleSkills project.
  • You want to automate the creation of pull requests for bug fixes or feature additions.
  • Your team follows a specific commit message format and needs consistent pull request generation.
  • You are working on a branch and ready to propose your changes as a pull request.

Key capabilities

  • Generates diffs between local and remote branches.
  • Formats commit messages.
  • Pushes changes to remote branches.
  • Creates pull requests.

Example prompts

  • "Create a pull request for my changes on the 'feature-branch' branch targeting the 'main' branch."
  • "Generate a pull request with the title 'Fix: Issue #123'."
  • "Submit a pull request after formatting commit messages according to PaddleSkills conventions."

Tips & gotchas

The skill requires proper configuration of remote repositories and authentication credentials for successful execution. Ensure your local branch is up-to-date with the target branch before initiating the pull request process.