contributor-workflow

Name: contributor-workflow
Availability: InStock
Author: cyanautomation

Execute a standardized contribution workflow from issue understanding to PR-ready validation.

1|Updated Jan 14, 2026

Search Tags:#workflow #contribution #contributing #lint #ci #pull-request #tests

Ready to run

npx skills add https://github.com/CyanAutomation/motioninocean --skill contributor-workflow

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps contributors follow a consistent, PR-ready workflow for motion-in-ocean, guiding from issue understanding to validated PR.

Core Features & Use Cases

Review README.md sections related to runtime assumptions, configuration, and local development; Review CONTRIBUTING.md for coding workflow, expected commands, and PR expectations; Implement the smallest coherent change; If behavior/config changed, update documentation in README.md (or adjacent docs) to keep user guidance accurate; Run baseline quality checks: make format, make lint, make type-check, make test; Validate app behavior on non-Pi environments using MOCK_CAMERA=true; Prepare final change summary with what changed, why, and how it was tested.

Quick Start

Follow the step-by-step workflow to identify impacted areas, implement the smallest coherent change, run the baseline checks, and prepare a PR-ready summary.

Frequently Asked Questions about contributor-workflow

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

FAQPage Schema

How do I standardize a contribution workflow from issue to pull request?▼

Standardize a contribution workflow by reviewing README.md and CONTRIBUTING.md, implementing the smallest coherent change, running baseline quality checks like make lint and make test, and preparing a validated PR summary.

What baseline quality checks should I run before submitting a pull request?▼

Run make format, make lint, make type-check, and make test as baseline quality checks before submitting a pull request to ensure code changes align with project standards and pass CI validation.

How do I validate app behavior on non-Pi environments before a pull request?▼

Validate app behavior on non-Pi environments before a pull request by running the application with MOCK_CAMERA=true to simulate hardware dependencies and ensure cross-platform compatibility.

Can I use this contribution workflow for documentation updates and bug fixes?▼

Yes, this contribution workflow supports code changes, documentation updates, bug fixes, and feature additions, requiring README.md updates if behavior or configuration changes to maintain accurate user guidance.

What's the best way to prepare a PR-ready change summary with testing evidence?▼

Prepare a PR-ready change summary by documenting what changed, why the modification was necessary, and how it was tested, ensuring the smallest coherent change is validated against CONTRIBUTING.md expectations.

Why does my contribution workflow require updating README.md for configuration changes?▼

Updating README.md for configuration changes is required because the contribution workflow enforces accurate user guidance, ensuring runtime assumptions and local development instructions reflect any modified behavior.