opencode-contributor

Automate the OpenCode contribution workflow from issue triage to PR drafting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thesobercoder/skills --skill opencode-contributor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-contributor
Source: https://github.com/thesobercoder/skills/tree/main/opencode-contributor
Command: npx skills add https://github.com/thesobercoder/skills --skill opencode-contributor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the OpenCode contribution workflow from repo identity checks through issue selection, implementation, verification, and PR drafting to reduce guesswork and ensure compliance with repo policies.

Core Features & Use Cases

  • End-to-end guidance from repo identity validation to PR drafting for anomalyco/opencode and forks.
  • Structured triage and viability checks to surface high-impact, small-scope changes.
  • Alignment with repo guidance (CONTRIBUTING.md, AGENTS.md, PR templates) to streamline maintainer review.

Quick Start

Start the OpenCode contribution workflow on anomalyco/opencode and follow the prompts to verify repo identity, triage issues, and draft a compliant PR.

Frequently Asked Questions about opencode-contributor

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

FAQPage Schema
How do I automate the OpenCode contribution workflow from issue triage to pull request?

Automating the OpenCode contribution workflow involves running an end-to-end process that verifies repository identity, triages issues via gh, explores code impact, and drafts pull requests with guardrails to ensure compliance with repo policies.

What is the process for triaging issues in the anomalyco/opencode repository?

Triage for anomalyco/opencode involves using gh to identify issues, applying structured viability checks to surface high-impact and small-scope changes, and following repo guidance from CONTRIBUTING.md and AGENTS.md to align contributions with maintainer expectations.

How do I draft a compliant pull request for OpenCode forks?

Drafting a compliant pull request for OpenCode forks requires following repo-specific PR conventions, aligning changes with CONTRIBUTING.md and PR templates, and applying built-in guardrails during implementation to ensure the submission meets all repository policy requirements.

Can I use this workflow to manage git worktrees when exploring code impact?

Yes, the workflow explicitly satisfies requirements to manage git worktrees, allowing you to safely explore code impact and test viable changes before finalizing your pull request draft for the anomalyco/opencode repository or its forks.

Does the OpenCode contribution workflow require specific dependencies or components?

No specific dependencies or components are required to run the OpenCode contribution workflow, as the process relies on standard git workflows and gh commands to manage repository identity checks, issue triage, and pull request drafting.