cli-contributor

Guide CLI repository contributors through local development workflows and validation practices.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/robertolopezlopez/agent-skills --skill cli-contributor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-contributor
Source: https://github.com/robertolopezlopez/agent-skills/tree/main/skills/cli/contributor
Command: npx skills add https://github.com/robertolopezlopez/agent-skills --skill cli-contributor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors make reliable changes in a CLI product repository by applying local development conventions, validation workflows, and merge request practices instead of relying on generic assumptions.

Core Features & Use Cases

  • Repository Workflow Guidance: Provides CLI-specific guidance for package manager selection, monorepo navigation, script discovery, and scoped implementation practices.
  • Testable Development Practices: Encourages dependency injection, avoiding hidden globals, test-first workflows, and appropriate validation with repository-defined commands.
  • Merge Request Support: Helps prepare engineer-focused summaries with change context, risk notes, and repository-aligned review expectations.

Quick Start

Use the cli-contributor skill to help me implement and validate a change in the CLI product repository following its local contributor conventions.

Frequently Asked Questions about cli-contributor

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

FAQPage Schema
How do I implement CLI changes in a TypeScript monorepo following local conventions?

Implement CLI changes in a TypeScript monorepo by navigating package scripts, applying dependency injection, and validating with repository-defined commands to ensure scoped, testable contributions aligned with local engineering processes.

What is the best way to prepare a merge request for a JavaScript CLI codebase?

Preparing a merge request for a JavaScript CLI codebase involves drafting engineer-focused summaries with change context, risk notes, and review expectations that adhere strictly to the repository's specific contributor workflows and validation practices.

How do I discover and run tests for a specific package in a CLI monorepo?

Discover and run tests in a CLI monorepo by locating repository-specific package scripts and utilizing local validation commands, ensuring you avoid hidden globals and maintain test-first workflows throughout the implementation process.

Does this contributor workflow support dependency injection patterns for testable CLI development?

Yes, this contributor workflow supports dependency injection patterns for testable CLI development by enforcing practices that avoid hidden globals, prioritize test-first workflows, and utilize repository-defined validation commands for reliable artifact-aware engineering.

Why should I use repository-specific workflows instead of generic assumptions for CLI contributions?

Using repository-specific workflows instead of generic assumptions for CLI contributions prevents validation errors and merge request rejections by enforcing local package manager selection, scoped changes, and artifact-aware engineering processes tailored to the codebase.