create-pr_skill

This skill automates PR work by analyzing changes, generating descriptions, signing off with DCO, and creating linked issues and PRs.
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openharmonyinsight/openharmony-skills --skill create-pr

  • SKILL.md3.3 KB

Overview

This skill automates the end-to-end pull request workflow for git projects. It analyzes code changes, generates structured Issue and PR descriptions, signs commits with DCO, pushes changes, and optionally creates and links Issues and PRs via platform APIs.

How this skill works

The script inspects git diffs to detect added, modified, or removed functions and classes and compiles file-level change stats. It auto-generates Issue and PR titles and bodies from the real diffs, creates a DCO-signed commit, pushes the branch, and uses the detected remote platform API (GitHub, GitLab/GitCode) to create an Issue and a PR that references the Issue with a Fixes #id link. If the API is unavailable, it falls back to opening the web PR creation page.

When to use it

  • You want consistent, detailed PR and Issue descriptions derived from actual diffs.
  • You need automated DCO sign-off on commits to meet contribution policies.
  • You want to reduce manual steps: commit, push, create Issue, create PR, and link them.
  • You maintain multiple platforms (GitHub, GitLab/GitCode) and want a single workflow.
  • You want an analyze-only mode to preview detected changes before committing.

Best practices

  • Set git user.name and user.email so DCO sign-off is accurate.
  • Configure a platform token via git config or environment variables with api/read_api/write_repository scope.
  • Run in a feature branch and verify the analyze-only output before auto-committing.
  • Use --no-commit or --no-push flags when integrating into CI or when you need manual control.
  • Review generated Issue/PR drafts to add context or testing details before final submission.

Example use cases

  • Feature branch workflow: run end-to-end to commit with DCO, push, create Issue, and open a linked PR automatically.
  • Small fixes: auto-generate a concise PR body and link to an auto-created Issue with a single command.
  • Open-source projects requiring DCO: ensure every automated commit includes Signed-off-by metadata.
  • CI helper: run in analyze-only mode in pipelines to produce a change summary without making repo changes.
  • Multi-platform repos: let the script detect remote and call the appropriate API for Issue/PR creation.

FAQ

Provide a platform token with api/read_api/write_repository permissions. Tokens can be set via git config, environment variables, or a tokens file.

How does DCO sign-off work?

The script appends a Signed-off-by line to commits using git user.name and git user.email; ensure those are configured to pass DCO checks.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational