skills.rest
yo-steven
yo-stevenCOMMUNITY
Explore all skills by this author →
GitHub

contributing

Standardize NeMo-RL pull request titles, signed commits, and CI triggering.

Updated May 23, 2026
Search Tags:#code review#pull request#conventional commits#contribution guidelines#git sign-off#CI triggering
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill contributing-yo-steven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contributing
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NeMo-RL/contributing
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill contributing-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents rejected pull requests and broken CI checks by standardizing how contributors format PR titles, create signed commits, and trigger verification.

Core Features & Use Cases

  • Conventional PR titles: Enforces a Conventional Commits-style title schema compatible with the repo’s semantic-pull-request CI check.
  • Commit sign-off: Requires signing commits with -s to support contribution provenance and policy compliance.
  • Deterministic CI triggering: Explains how to request CI for a specific full commit SHA using the /ok to test comment workflow during PR review.

Quick Start

Open your NeMo-RL pull request using a Conventional Commits-formatted PR title, make a signed commit with git commit -s, and trigger CI by commenting /ok to test <full-commit-sha> after you push.

Frequently Asked Questions about contributing

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

FAQPage Schema
How do I format a pull request title for NeMo-RL to pass CI checks?▼

You must format NeMo-RL pull request titles using the Conventional Commits schema to pass the repository's semantic-pull-request CI check. This standardizes PR authoring and prevents automated validation failures.

Why do I need to sign commits with git commit -s for contribution guidelines?▼

You need to sign commits with `git commit -s` to support contribution provenance and policy compliance within NeMo-RL. This sign-off requirement verifies code origin during pull request reviews.

How do I trigger CI on a specific commit during a pull request review?▼

You trigger CI by commenting `/ok to test <full-commit-sha>` on your pull request, providing the full commit SHA. This deterministic mechanism ensures verification runs only when explicitly requested.

What is the conventional commits workflow for reducing pull request friction?▼

The workflow reduces pull request friction by enforcing Conventional Commits-style PR titles, requiring `git commit -s` sign-offs, and using the `/ok to test` comment for CI triggering. This prevents rejected pull requests and broken CI checks.

Can I trigger CI validation without a full commit SHA in NeMo-RL?▼

No, deterministic CI triggering requires the exact full commit SHA. You must use the `/ok to test <full-commit-sha>` comment mechanism during PR review to request verification for a specific commit.

Related Skills

Explore More Legal & Compliance Skills→
alexandremendoncaalvaroalexandremendoncaalvaro
728

ad-commit

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

Community
Advanced
nicolehaugennicolehaugen

pr-review-response

Generate pull request review comment replies linked to commit SHAs.

Community
Advanced
NinaVerdeNinaVerde

CI Sentinel

Enforce Conventional Commits standards for PR titles and commit messages in Flutter GitHub workflows.

Community
Intermediate
CyapstayeCyapstaye
9

github-pr-workflow

Manage the GitHub pull request lifecycle with automated merging and CI monitoring.

Community
Advanced