skills.rest
zzstoatzz
zzstoatzzCOMMUNITY
Explore all skills by this author →
GitHub

contribute

Guide developers through forking, configuring, testing, and submitting pull requests for plyr.fm.

16|4|Updated Oct 31, 2025
Search Tags:#git#code-review#contribute#open-source#pull-request#local-development
One-click install
npx skills add https://github.com/zzstoatzz/plyr.fm --skill contribute-zzstoatzz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contribute
Source: https://github.com/zzstoatzz/plyr.fm/tree/main/.claude/skills/contribute
Command: npx skills add https://github.com/zzstoatzz/plyr.fm --skill contribute-zzstoatzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps new and existing contributors navigate the plyr.fm codebase, align on project rules, and set up local development to fix bugs, add features, or open PRs.

Core Features & Use Cases

  • Orientation: understand project structure, stack, and conventions.
  • Setup: fork, clone, and run local dev environment using uv, bun, and just.
  • Collaboration: open PRs with clear context and tests to improve plyr.fm.

Quick Start

Fork the repository, set up the local development environment, and open a pull request with a clear description.

Frequently Asked Questions about contribute

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

FAQPage Schema
How do I set up local development for plyr.fm to contribute code?▼

You can set up local development for plyr.fm by forking the repository, configuring your environment with uv, bun, and just, and running the local dev server to validate changes before submitting a pull request.

What is the proper workflow to submit a pull request to plyr.fm?▼

The pull request workflow for plyr.fm requires validating changes locally, writing tests, and opening a PR with clear context and descriptions to enforce a safe, documented contribution process.

Do I need uv and bun to contribute to plyr.fm?▼

Yes, contributing to plyr.fm requires uv and bun to configure the local development environment, alongside the just command runner, ensuring proper stack alignment and test execution.

What conventions should I follow when contributing to plyr.fm?▼

Contributing to plyr.fm requires following documented project rules, understanding the specific project structure and stack, and ensuring all pull requests include clear context and appropriate tests.

Why does my local development environment fail when contributing to plyr.fm?▼

Local development for plyr.fm can fail if uv, bun, or just are not properly configured, or if the documented contribution workflow and validation steps are not followed before opening a pull request.

Related Skills

Explore More Software Engineering Skills→
BailipaBailipa
4

setup-pre-commit

Automate pre-commit hook setup with Husky, lint-staged, and Prettier.

Community
Intermediate
duongtdnduongtdn

devloop:pr-fix

Automate GitHub pull request review comment fixes with local test verification.

Community
Advanced
ialamehialameh
2

quality-gates

Validate code changes against project quality standards and output a structured report.

Community
Advanced
jamesjlundinjamesjlundin
32

pr-review

Analyze pull requests and generate structured review reports.

Community
Intermediate