skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
bostonaholic/team79 installs

team-pr

Use for opening PRs only on explicit request. Never infer from passed verification. Commits, updates an existing changelog, pushes, and opens a draft PR per repo.

How do I install this agent skill?

npx skills add https://github.com/bostonaholic/team --skill team-pr
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill automates the creation and management of pull requests, including changelog updates, screenshot attachments, and posting review findings as PR comments. It follows secure coding practices by using local scripts for data processing and explicitly instructing the AI to treat external file content as data rather than executable instructions. It identifies a potential surface for indirect prompt injection from review records but includes design-level mitigations.

  • Socketpass

    No alerts

  • Snykfail

    Risk: CRITICAL · 2 issues

What does this agent skill do?

Team PR — Create the Pull Request

Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.

Before finalizing prose you author, read the writing standards. Preserve exact commands, tokens, and templates.

Two modes:

  • Resume mode — $ARGUMENTS/1-task.md and $ARGUMENTS/6-design.md exist. Execution step 3 binds one review status from the newest review-<n>.md and one security status from the newest security-review-<n>.md.
  • Standalone mode — no matching artifact directory, but the working tree has commits or staged changes ready to ship. The current branch is the work source.

Core contracts

Each is detailed in Execution at the step named.

  1. Update an existing CHANGELOG.md under ## [Unreleased] after step 3 binds the review and security statuses, and commit before opening any PR; never create one (step 6).
  2. Open a draft PR automatically — do not stop to ask (step 7), then report the PR and how to mark it ready for review.
  3. Multi-repo: one draft PR per repo with commits, then a refresh of each with the companion PR links (step 8). Tracking rules own the in-review transition and the home-only closing rule.
  4. After each later push to an open PR, run the step order again and refresh each PR's body (step 10).
  5. A branch that impacts a UI always carries screenshots (step 4).
  6. Deferred findings and cross-model dispositions are comments on the home PR, never the body: run review comments after open and after each refresh; a refresh posts only missing comments.
  7. Subagents and inline work split per Execution ## Step dispatch.

Procedure references

Read each reference completely when reaching that stage, in order.

  1. Input
  2. Execution
  3. Screenshot Upload
  4. Changelog Update
  5. Commit Discipline
  6. Review Comments

Applied principles

Read and apply: focused work rules.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/bostonaholic/team/team-pr">View team-pr on skillZs</a>