spotiarr-workflow

Enforce spotiarr contribution rules for branches, PRs, and local validation.

41|6|Updated Nov 27, 2025

Search Tags:#pull request #github #pnpm #secrets management #branch naming #ci validation #frontend backend

Ready to run

npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spotiarr-workflow
Source: https://github.com/mralexsaavedra/spotiarr/tree/main/skills/spotiarr-workflow
Command: npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or unsafe contributions to the spotiarr repo by enforcing consistent branch naming, PR verification, and secret-handling rules during day-to-day development.

Core Features & Use Cases

CI-ready workflow enforcement: Keeps lint, tests, and builds separated into distinct jobs for predictable quality gates.
Validation paths by scope: Ensures the correct pnpm command sequences for frontend-only, backend-only, and cross-workspace changes.
Guardrails for safety and correctness: Blocks committing credentials and avoids bypassing pre-commit hooks while standardizing PR content (what/why/verification and screenshots for UI work).

Quick Start

Apply the spotiarr-workflow rules before opening a pull request by creating a properly prefixed branch, running the correct lint/test/build sequence for your change scope, and confirming you did not commit any secrets.

Frequently Asked Questions about spotiarr-workflow

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

FAQPage Schema

How do I enforce safe pull request workflows for pnpm monorepos?▼

To enforce safe pull request workflows for pnpm monorepos, apply standardized branch-prefix conventions, separate lint/test/build CI validation gates, and strict no-secrets policies prior to opening a pull request.

What pnpm command sequences should I run for frontend and backend changes?▼

For frontend and backend changes, you must run validation paths scoped to your workspace changes. Ensure you execute the correct pnpm command sequences for frontend-only, backend-only, or cross-workspace modifications before submitting.

How do I format Conventional Commits PR titles for cross-workspace changes?▼

To format Conventional Commits PR titles for cross-workspace changes, standardize your PR content to include what, why, and verification details. This satisfies repository requirements for predictable quality gates when preparing your pull request.

Why does CI validation require separate lint, test, and build jobs?▼

CI validation requires separate lint, test, and build jobs to maintain predictable quality gates. This separation enforces a repeatable contribution workflow and ensures local validation passes prior to the CI pipeline running.

Can I bypass pre-commit hooks when preparing a pull request?▼

No, you cannot bypass pre-commit hooks when preparing a pull request. The workflow enforces strict guardrails for safety and correctness, actively blocking commits that bypass hooks or contain credentials and secrets.