Skip to content

fix: remove PR/review-request instructions from update skills #391

@captainsafia

Description

@captainsafia

Summary

The "update skills" (e.g. update-pr-review, update-skill, update-open-api-spec, etc.) currently instruct agents to request reviews or open pull requests directly. This should be removed in favor of pushing a branch and relying on the deterministic workflow to open the PR and tag the appropriate reviewers based on the config.

Problem

Skills that instruct agents to open PRs or tag reviewers manually:

  • Bypass the deterministic PR-opening workflow
  • Can result in inconsistent reviewer assignment
  • Duplicate logic that is better owned by the automated workflow

Proposed Change

Audit all update-* skills and remove any instructions that tell the agent to:

  • Open or create a pull request
  • Request reviews from specific individuals or teams

Instead, the skills should instruct agents to push their branch and let the deterministic workflow handle PR creation and reviewer assignment based on the configured CODEOWNERS or reviewer config.

Metadata

Metadata

Assignees

Labels

area:workflowGitHub workflows, Python automation, or Oz integrationbugSomething isn't workingdocumentationImprovements or additions to documentationready-to-implementIndicates that an issue is ready for a code implementation coupled with the associated plan.repro:highThe report looks highly reproducible from the available informationtriagedInitial Oz triage has been completed for this issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions