skills.rest
bga23
bga23COMMUNITY
Explore all skills by this author →
GitHub

nemoclaw-contributor-create-pr

Create GitHub pull requests conforming to the NemoClaw PR template via gh CLI.

Updated Aug 23, 2026
Search Tags:#automation#workflow#template#pull request#github#pr#dco
One-click install
npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-contributor-create-pr-bga23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-create-pr
Source: https://github.com/bga23/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-create-pr
Command: npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-contributor-create-pr-bga23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates creating GitHub pull requests that conform to the NemoClaw PR template, ensuring PR metadata, checks, and body formatting are consistent across contributions.

Core Features & Use Cases

  • Create PRs via the gh CLI that strictly follow NemoClaw's PR template.
  • Validate branch state, run pre-PR checks, push to remote, and assemble a correctly formatted PR body.
  • Support standard PR workflows including Conventional Commits style titles, DCO sign-off, and an AI-assisted disclosure when applicable.

Quick Start

Prepare your feature branch, ensure commits are ready, and run the PR creation workflow using the gh CLI with the pre-formatted template.

Frequently Asked Questions about nemoclaw-contributor-create-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request creation with a strict PR template?▼

Automating GitHub pull request creation involves validating the branch state, running pre-PR checks, pushing to remote, and composing a PR body against a required template using the gh CLI with strict metadata and DCO sign-off.

What is DCO sign-off and how does it apply to automated GitHub PR workflows?▼

DCO sign-off in automated GitHub PR workflows certifies that the contributor authored or has rights to the code, applied within the pull request creation process to maintain compliance and standardized metadata.

How do I validate a branch state before pushing to remote for a pull request?▼

Validating branch state before pushing to remote involves running pre-PR checks to ensure commits are ready, confirming the feature branch is prepared, and verifying the repository state conforms to the required contribution workflow.

Can I use Conventional Commits style titles with gh CLI pull request automation?▼

Yes, you can use Conventional Commits style titles with gh CLI pull request automation, composing standardized PR titles and bodies that conform to strict template requirements during the end-to-end PR creation workflow.

What are the limitations of enforcing PR templates via GitHub automation?▼

Enforcing PR templates via GitHub automation is limited to collaborative software development workflows, requiring prepared feature branches and ready commits, and may not accommodate template formats or contribution processes outside the standardized NemoClaw structure.

Related Skills

Explore More Software Engineering Skills→
shiimanshiiman
6

pr-creator

Create pull requests and close related issues using Conventional Commits.

Community
Intermediate
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
alexandremendoncaalvaroalexandremendoncaalvaro
728

ad-commit

Draft atomic Conventional Commits with DCO Signed-off-by sign-off.

Community
Advanced
y-miyazakiy-miyazaki
4

github-pr-overview

Update GitHub Pull Request body sections using provided scripts.

Community
Intermediate