Skip to content
TrustedSkillsbeta
Back to all skills

Qe Release

Checked
proffesor-for-testing·vlatest·devops·MIT

Qe Release automates deployment of QE test results to designated environments, streamlining verification and accelerating feedback loops.

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 proffesor-for-testing/agentic-qe --skill qe-release -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

proffesor-for-testing

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 proffesor-for-testing/agentic-qe at 124d8c735e.

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

Commit
124d8c735e
Manifest
.kiro/skills/qe-release/SKILL.md
Scanned
1 file, 61 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

The qe-release skill automates software release processes, handling tasks like version bumping, tag creation, and deployment to staging or production environments. It streamlines releases by reducing manual steps and potential errors associated with traditional methods. This skill aims to improve the speed and reliability of your software delivery pipeline.

When to use it

  • Automating a new feature release to a staging environment for testing.
  • Triggering a full production deployment after successful completion of automated tests.
  • Creating versioned releases based on Git tags (e.g., v1.2.3).
  • Managing the promotion of builds across different environments (dev, staging, prod).

Key capabilities

  • Version bumping (semantic versioning)
  • Git tag creation
  • Deployment to specified environments (staging, production)

Example prompts

  • "Release version 1.2.3 to the staging environment."
  • "Create a Git tag for the latest commit and deploy to production."
  • "Bump the patch version and release to staging."

Tips & gotchas

The skill requires appropriate permissions within your repository and deployment environments. Ensure that the AI agent has access to perform these actions safely and effectively.