netscript-pr

Automate NetScript pull request creation with templated bodies and issue closing.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/rickylabs/netscript --skill netscript-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netscript-pr
Source: https://github.com/rickylabs/netscript/tree/main/.agents/skills/netscript-pr
Command: npx skills add https://github.com/rickylabs/netscript --skill netscript-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of authoring and managing pull requests for NetScript projects, ensuring consistency in branch naming, PR bodies, comments, and labels, and automating issue closing.

Core Features & Use Cases

  • Branch Naming Conventions: Automates branch naming according to NetScript standards.
  • PR Body Templates: Provides templates for PR bodies with structured sections for summary, scope, slices, validation, and closing issues.
  • Issue Closing Automation: Automatically closes issues when PRs are merged based on defined keywords in the PR body.
  • Label Taxonomy: Manages a comprehensive label taxonomy for issues and PRs to organize workflow stages and areas.
  • Milestones: Assigns milestones to issues based on release schedules and wave labels.
  • Use Case: For a developer working on a NetScript project, this Skill ensures that all pull requests are consistent with the project's standards and automates the closing of related issues upon merge.

Quick Start

Use the netscript-pr skill to create a new pull request for a feature branch and automatically populate the PR body with the required sections and labels.

Frequently Asked Questions about netscript-pr

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

FAQPage Schema
How do I automate pull request creation and issue closing for NetScript projects?

Automating pull request creation for NetScript projects requires standardized branch naming, PR body templating, and keyword-based issue closing. This Skill uses GitHub API integration to format PRs consistently and close related issues automatically upon merge.

What's the best way to enforce consistent PR body formatting and label taxonomy in GitHub?

Enforcing consistent PR body formatting requires structured templates with summary, scope, slices, and validation sections. This Skill provides standardized PR body templates and manages a comprehensive label taxonomy to organize workflow stages and areas for NetScript repositories.

How does issue closing automation work when a pull request is merged?

Issue closing automation works by scanning defined keywords in the PR body to trigger closure upon merge. This Skill identifies these keywords within the populated PR templates and automatically closes the linked issues via the GitHub API.

Do I need GitHub API integration to manage NetScript milestones and branch naming conventions?

GitHub API integration is required to manage NetScript branch naming conventions and assign milestones based on release schedules. This Skill relies on the github-api dependency to automate branch naming and apply wave labels to issues.

Can I use this Skill for NetScript issue management without predefined PR body templates?

Using this Skill for NetScript issue management without predefined PR body templates bypasses its core automation logic. The issue closing mechanism and milestone assignments depend directly on the structured sections and defined keywords populated within the PR body templates.