Create Pr
ListedAutomatically generates pull requests in OpenHarmony based on insights from code analysis and identified improvements.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add openharmonyinsight/openharmony-skills --skill create-pr -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
openharmonyinsight
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.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.gitcode.com, gitcode.com.
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.
Hosts contacted
api.github.comsource hostgitcode.comundeclaredapi.gitcode.comundeclaredgitlab.comsource hostWhat it found
- skills/create-pr/references/platform-apis.md:201contacts gitcode.com
curl "https://gitcode.com/api/v4/projects/owner%2Frepo/issues?per_page=100&page=1" - skills/create-pr/scripts/repo_api.py:139contacts api.gitcode.com
return "https://api.gitcode.com/api/v5" - skills/create-pr/scripts/repo_api.py:144contacts api.gitcode.com
return "https://api.gitcode.com/api/v5"
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 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 openharmonyinsight/openharmony-skills at 5ae988cab6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5ae988cab6
- Manifest
- skills/create-pr/SKILL.md
- Scanned
- 7 files, 3,052 lines
About this skill
What it does
This skill automates the creation of pull requests (PRs) in OpenHarmony repositories. It can generate PR titles and descriptions based on provided information, streamlining the contribution workflow for developers. The tool simplifies the process of submitting code changes and ensuring proper documentation within OpenHarmony projects.
When to use it
- You've made changes to an OpenHarmony repository and want to quickly create a pull request.
- You need assistance generating a descriptive title and body for your pull request.
- You are collaborating with others on OpenHarmony development and want to standardize the PR creation process.
- You’re automating a build or testing workflow that requires creating a PR upon completion.
Key capabilities
- Automated PR title generation
- Automated PR description generation
- Integration with OpenHarmony repositories
- Streamlined contribution workflow
Example prompts
- "Create a pull request for my changes to the camera module, focusing on improved low-light performance."
- "Generate a PR with the title 'Fix: Incorrect date format in settings' and describe the bug fix implemented."
- “Create a PR based on these code diffs, targeting the main branch.”
Tips & gotchas
- Ensure you have appropriate permissions to create pull requests within the target OpenHarmony repository.
- The quality of the generated title and description depends on the clarity and detail provided in your prompt.