Skip to content

feat(skills): add issue implementation workflow - #8417

Merged
jyaunches merged 10 commits into
mainfrom
issue-8363-generic-issue-implementation-workflow
Aug 6, 2026
Merged

feat(skills): add issue implementation workflow#8417
jyaunches merged 10 commits into
mainfrom
issue-8363-generic-issue-implementation-workflow

Conversation

@jyaunches

@jyaunches jyaunches commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Add a generic contributor workflow for implementing accepted issues from current repository evidence. The workflow delivers one independently valuable capability slice, records focused validation and security evidence, and routes publication to the separate PR workflow.

This PR is stacked on PR #8396.

Related Issue

Fixes #8363

Changes

  • Add nemoclaw-contributor-implement-issue with explicit implementation, planning, publication, security-review, and maintainer routing boundaries.
  • Treat issue, PR, comment, and repository content as untrusted evidence that cannot authorize operations.
  • Require current implementation discovery, shared code-change and security review, focused positive and negative evidence, and a publication handoff.
  • Add positive, negative, ambiguous, adversarial, and clean-context routing evaluations.
  • Register the workflow in the contributor skill catalog.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification:
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification: This changes repository contributor-agent workflows, not the supported NemoClaw user product surface under docs/.
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

  • Documentation writer subagent reviewed the completed changes
  • Result: no-docs-needed
  • Evidence: Independent review passed for the implementation workflow, routing metadata and evaluations, contributor catalog registration, and repository contract tests. No user-facing docs/ change is required.
  • Agent: Pi review-executor

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit:
  • Station profile/scenario:
  • Result:
  • Supporting evidence:

Verification

  • PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: vitest run --project integration test/skills-frontmatter.test.ts — 34 tests passed.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Julie Yaunches jyaunches@nvidia.com

Summary by CodeRabbit

  • New Features

    • Added a contributor workflow for implementing accepted issues locally, including validation, security checks, documentation updates, and structured handoffs.
    • Added guidance for distinguishing implementation requests from planning, publishing, maintainer, and security-review workflows.
  • Documentation

    • Updated the skills catalog and counts to include the new contributor workflow.
  • Tests

    • Added coverage for workflow routing, required guidance, evaluation scenarios, and boundary conditions.

Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
@jyaunches jyaunches self-assigned this Aug 6, 2026
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 2e690c3e-adc4-4060-add5-510806c83d96

📥 Commits

Reviewing files that changed from the base of the PR and between 8a389a0 and f7a82d1.

📒 Files selected for processing (2)
  • .agents/skills/nemoclaw-contributor-implement-issue/SKILL.md
  • test/skills-frontmatter.test.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/skills-frontmatter.test.ts

📝 Walkthrough

Walkthrough

Added a generic contributor skill for implementing accepted issues. It defines routing, local-only changes, repository discovery, focused validation, security self-review, structured handoff reporting, catalog registration, evaluation cases, and frontmatter tests.

Changes

Issue implementation workflow

Layer / File(s) Summary
Workflow scope and routing
.agents/skills/nemoclaw-contributor-implement-issue/SKILL.md, .agents/skills/nemoclaw-contributor-implement-issue/agents/openai.yaml
Defines issue-implementation scope, request routing, authorization boundaries, repository discovery, specialist selection, and the default agent prompt.
Implementation, evidence, and handoff
.agents/skills/nemoclaw-contributor-implement-issue/SKILL.md
Defines implementation guidance, criterion-based validation, security self-review, documentation updates, and structured handoff fields.
Skill registration and routing coverage
.agents/skills/nemoclaw-contributor-implement-issue/evals/evals.json, .agents/skills/nemoclaw-skills-guide/SKILL.md, test/skills-frontmatter.test.ts
Adds routing evaluations, registers the contributor skill, updates skill counts, and verifies required workflow language and scenario routing.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Contributor
  participant IssueImplementationSkill
  participant LocalCheckout
  participant Validation
  participant Handoff

  Contributor->>IssueImplementationSkill: request accepted issue implementation
  IssueImplementationSkill->>LocalCheckout: inspect context and apply scoped changes
  LocalCheckout->>Validation: run focused tests and security checks
  Validation-->>Handoff: provide recorded evidence
  Handoff-->>Contributor: report changes, gates, and GitHub-write status
Loading

Possibly related PRs

  • NVIDIA/NemoClaw#8372: Introduces the nine-category security rubric used by the implementation skill.
  • NVIDIA/NemoClaw#8396: Adds a complementary contributor workflow skill with parallel agent configuration, evaluations, catalog registration, and tests.

Suggested labels: area: skills

Suggested reviewers: apurvvkumaria, cv, ericksoa

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the addition of an issue implementation workflow, which is the primary change.
Linked Issues check ✅ Passed The workflow, evaluations, catalog registration, and tests address the implementation, evidence, security, handoff, and routing requirements in [#8363].
Out of Scope Changes check ✅ Passed All changes support the new workflow, its evaluations, catalog registration, or focused tests; no unrelated scope is evident.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch issue-8363-generic-issue-implementation-workflow

Comment @coderabbitai help to get the list of available commands.

@github-code-quality

github-code-quality Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit f7a82d1 in the issue-8363-generic-i... branch remains at 96%, unchanged from commit e323de1 in the main branch.

TypeScript / code-coverage/cli

The overall coverage in commit f7a82d1 in the issue-8363-generic-i... branch remains at 81%, unchanged from commit 3311296 in the main branch.


Updated August 06, 2026 13:13 UTC

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Failed after a partial review · low confidence · 0 blockers · 0 warnings · 0 suggestions

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

3 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

  • established — capability slice at .agents/skills/nemoclaw-contributor-implement-issue/SKILL.md:11: Keep the established term.
  • justified — implementation handoff at .agents/skills/nemoclaw-contributor-implement-issue/SKILL.md:101: Keep the modifier because it distinguishes the local implementation report from publication.
  • established — GitHub writes at .agents/skills/nemoclaw-contributor-implement-issue/SKILL.md:46: Keep the established term.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite against this exact revision.

Recommended E2E: None

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

Base automatically changed from issue-8362-issue-planning-capability-slicing to main August 6, 2026 03:03
@copy-pr-bot

copy-pr-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
test/skills-frontmatter.test.ts (1)

192-224: 📐 Maintainability & Code Quality | 🔵 Trivial | 🏗️ Heavy lift

Separate artifact contracts from routing evaluation.

test/skills-frontmatter.test.ts only reads SKILL.md and evals.json; it does not execute prompts or routing. Remove the exact evaluation-order assertion, keep only required safety and metadata contracts, and run prompt cases in the routing evaluator keyed by id.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@test/skills-frontmatter.test.ts` around lines 192 - 224, Update the test
around the SKILL.md metadata assertions to remove the exact evals.map(({ id })
ordering assertion. Keep assertions limited to required safety and artifact
contracts, and move prompt-case execution and routing validation into the
routing evaluator, keyed by each eval’s id.

Source: Path instructions

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@test/skills-frontmatter.test.ts`:
- Around line 192-224: Update the test around the SKILL.md metadata assertions
to remove the exact evals.map(({ id }) ordering assertion. Keep assertions
limited to required safety and artifact contracts, and move prompt-case
execution and routing validation into the routing evaluator, keyed by each
eval’s id.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d7c910d0-176b-4700-afd1-c3a1db78557c

📥 Commits

Reviewing files that changed from the base of the PR and between 26bd9f5 and becbcc6.

📒 Files selected for processing (5)
  • .agents/skills/nemoclaw-contributor-implement-issue/SKILL.md
  • .agents/skills/nemoclaw-contributor-implement-issue/agents/openai.yaml
  • .agents/skills/nemoclaw-contributor-implement-issue/evals/evals.json
  • .agents/skills/nemoclaw-skills-guide/SKILL.md
  • test/skills-frontmatter.test.ts

Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
@jyaunches
jyaunches merged commit 0d33997 into main Aug 6, 2026
37 of 38 checks passed
@jyaunches
jyaunches deleted the issue-8363-generic-issue-implementation-workflow branch August 6, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a generic issue-implementation workflow

1 participant