create-pr
Create GitHub Pull Requests in Japanese
Manual PR setup can miss changed files, tests, or repository conventions. This skill guides a Japanese-language workflow for review, commit, push, and GitHub PR creation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "create-pr" from https://skillstore.io/skills/0tarof-create-pr.md and its manifest at https://skillstore.io/api/skills/0tarof-create-pr/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "create-pr". Create a PR for the current changes.
Expected outcome:
The skill reviews changed files, asks for staging confirmation, creates a commit, pushes the branch, and returns the PR link.
Using "create-pr". Use the repository PR template.
Expected outcome:
The skill checks for a template, drafts each required section from the diff, and asks for title and body approval.
Using "create-pr". A required check fails before commit.
Expected outcome:
The skill stops the workflow, explains the failure in Japanese, and suggests the next repair step.
Security Audit
Medium RiskMost static backtick and URL alerts are Markdown examples or attribution links. Real risks remain where the workflow runs repo-controlled commands, commits, pushes, and creates GitHub pull requests. No prompt injection, exfiltration intent, or obfuscated payload was found in SKILL.md.
Confirmed security concerns (1)
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (22)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0tarof-create-pr/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0tarof-create-pr?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0tarof-create-pr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0tarof-create-pr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0tarof-create-pr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
0tarof. (2026). create-pr security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0tarof-create-pr/audits/7BibTeX citation
@techreport{0tarof-0tarof-create-pr-2026,
author = {0tarof},
title = {create-pr security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/0tarof-create-pr/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "create-pr security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "0tarof"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/0tarof-create-pr/audits/7"
identifiers:
- type: other
value: "skillstore:0tarof-create-pr:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
7 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-create-pr
2026-08-21
getsentry-create-pr
2026-08-21
crearize-create-pr
2026-08-21
cloud-officer-create-pr
2026-08-21
davila7-create-pr
2026-08-21
cygnusfear-create-pr
2026-08-21
0tarof-create-pr
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Feature Branch PR
Prepare a reviewed branch, run checks, commit approved files, and open a PR.
Dotfiles Maintenance
Validate Brewfile or script changes before creating a pull request.
Japanese Review Workflow
Keep PR preparation, error explanations, and confirmation requests in Japanese.
Try These Prompts
Create a pull request for my current branch. Review the diff first, then ask before staging, committing, pushing, and opening the PR.
Prepare this branch for a PR. Read the project instructions, identify required checks, run approved checks, and stop if any check fails.
Create a PR using the repository template. Fill each section from the current changes and ask me to confirm the title and body.
Create a release pull request from these changes. Group the summary by feature, fix, and maintenance work, then verify tests before pushing.
Best Practices
- Review the diff before approving staging or commit creation.
- Run required tests and linters before pushing the branch.
- Confirm the PR title, body, and branch before creation.
Avoid
- Do not stage every file without reviewing the diff.
- Do not skip failing checks to create a PR faster.
- Do not use it where push access is not intended.