Skip to content
TrustedSkillsbeta
Back to all skills

Qe Github Release Management

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

Helps with GitHub, management as part of automating DevOps pipelines and CI/CD workflows workflows.

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-github-release-management -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-github-release-management/SKILL.md
Scanned
1 file, 996 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 GitHub release management tasks. It can create, edit, and publish releases, including generating release notes from provided commit messages or files. The agent can also manage pre-release versions and associated assets.

When to use it

  • Automate the creation of new software releases based on a defined schedule.
  • Generate release notes automatically by parsing commit history.
  • Manage beta or alpha releases with specific version identifiers (e.g., "beta", "rc").
  • Upload pre-built binaries or other assets to GitHub releases.

Key capabilities

  • Create new GitHub Releases
  • Edit existing GitHub Releases
  • Publish GitHub Releases
  • Generate release notes from commit messages
  • Manage pre-release versions (e.g., beta, rc)
  • Upload assets to releases

Example prompts

  • "Create a new GitHub release for version 1.2.3 with the title 'Feature X Release'."
  • "Generate release notes for the latest commit history and publish release v2.0.0."
  • “Publish a beta release, version 1.0.0-beta.1, including the compiled binaries.”

Tips & gotchas

  • Ensure the AI agent has appropriate permissions (repo access) configured in GitHub to perform these actions.
  • The quality of automatically generated release notes depends on well-formatted commit messages.