maintainer-review

Assess demonstrated user need in node-redis GitHub issues and pull requests.

17.6k|2.0k|Updated Sep 14, 2010
One-click install
npx skills add https://github.com/redis/node-redis --skill maintainer-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintainer-review
Source: https://github.com/redis/node-redis/tree/main/.agents/skills/maintainer-review
Command: npx skills add https://github.com/redis/node-redis --skill maintainer-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates inconsistent, time-consuming maintainer reviews for node-redis GitHub issues and pull requests by enforcing evidence-based assessment of demonstrated user need before evaluating implementation quality, reducing unnecessary maintenance burden and ensuring work is prioritized on real user impact.

Core Features & Use Cases

  • Structured Need Assessment: Classifies issue/PR need evidence as Demonstrated, Plausible but unproven, Already covered, or Unsupported, and distinguishes capability gaps from ergonomics or discoverability gaps.
  • Lifecycle and Concurrency Validation: Runs mandatory interleaving and ownership passes for patches that modify cleanup, retry, or shared state to prevent cross-operation regressions.
  • Competing PR Evaluation: Compares overlapping PRs against need coverage, correctness, placement, and maintenance cost to recommend the single best implementation path.
  • Use Case: A node-redis maintainer can use this Skill to quickly assess a new PR for a Redis JSON feature, verify if the requested outcome is already achievable with existing APIs, check for concurrency risks in the patch, and decide if it is merge-worthy or should be closed in favor of a simpler alternative.

Quick Start

Use the maintainer-review skill to assess the GitHub issue or pull request at https://github.com/redis/node-redis/issues/1234 and provide a maintainer decision with a comment draft if closure or changes are needed.

Frequently Asked Questions about maintainer-review

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

FAQPage Schema
How do I evaluate node-redis pull requests for merge readiness?

Evaluate node-redis pull requests by enforcing evidence-based assessment of demonstrated user need, running mandatory concurrency and cleanup ownership checks, and calibrating merge recommendations by severity to ensure patches address real user impact.

What is the best way to triage node-redis GitHub issues?

Triage node-redis GitHub issues by classifying need evidence as Demonstrated, Plausible but unproven, Already covered, or Unsupported, and distinguishing capability gaps from ergonomics or discoverability gaps to eliminate low-value patch-first reviews.

How do I compare competing node-redis pull requests for the same feature?

Compare competing node-redis pull requests by evaluating need coverage, correctness, placement, and maintenance cost to recommend the single best implementation path instead of reviewing overlapping patches individually.

How do I check node-redis patches for concurrency and cleanup ownership risks?

Check node-redis patches for concurrency risks by running mandatory interleaving and ownership passes on modifications to cleanup, retry, or shared state to prevent cross-operation regressions before merging.

Can I draft maintainer comments for closing node-redis issues automatically?

Draft maintainer comments for closing node-redis issues by generating severity-calibrated feedback based on structured need assessment and alternative design comparisons aligned with repository maintainer standards.