pull-request

Standardize EEGLAB pull request descriptions and enforce pre-push MATLAB/Octave validation.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/MarvinCui/NeuroForge --skill pull-request-marvincui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/MarvinCui/NeuroForge/tree/main/NeuroForge/skills/eeglab/references/documentation/other
Command: npx skills add https://github.com/MarvinCui/NeuroForge --skill pull-request-marvincui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents EEGLAB pull requests from being rejected or delayed by enforcing a consistent PR format and a practical pre-push validation checklist.

Core Features & Use Cases

  • PR Description Standardization: Forces short plain-text PR titles and bodies with strict formatting rules to improve reviewer scanning and automation compatibility.
  • Issue-Linking Guidance: Clarifies when to use Fixes or Part of links so PRs accurately reflect scope and impact.
  • Pre-Push Validation Checklist: Recommends the narrowest meaningful MATLAB or Octave smoke checks to catch common failures (e.g., load + dataset integrity checks) before pushing.

Quick Start

Use this skill to draft a plain-text EEGLAB PR description that follows the required format and run the recommended MATLAB or Octave smoke validation before pushing changes.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I format an EEGLAB pull request description to pass code review on GitHub?

EEGLAB pull request descriptions require short plain-text titles and bodies with strict formatting rules to ensure GitHub code review processes receive consistent and actionable changes.

What pre-push validation should I run for EEGLAB code changes in MATLAB or Octave?

Pre-push validation for EEGLAB requires running MATLAB or Octave smoke tests that execute eeglab('nogui') and eeg_checkset on relevant sample data to verify dataset integrity.

When should I use Fixes versus Part of links in an EEGLAB pull request?

Use Fixes links when an EEGLAB pull request completely resolves an issue, and Part of links when changes represent partial scope, ensuring accurate impact tracking during code review.

Does the EEGLAB pull request workflow require running CI checks locally before pushing?

Yes, running local MATLAB or Octave smoke checks before pushing validates data paths and catches common failures early, ensuring the CI process receives tested EEGLAB modifications.

Can I use rich text formatting in EEGLAB GitHub pull request titles and bodies?

No, EEGLAB pull request standardization enforces plain-text constraints for titles and bodies, improving reviewer scanning speed and maintaining automation compatibility for validation.

Why do EEGLAB pull requests get delayed or rejected during code review?

EEGLAB pull requests get delayed when descriptions lack consistent formatting, miss correct issue-linking semantics, or skip pre-push MATLAB validation checks on modified data paths.