contributing

Guide contributors through pull request submission and torch skill authoring workflows.

5|Updated Apr 9, 2026

Search Tags:#documentation #quality #contribute #pull-request #torch #skill-authoring

Ready to run

npx skills add https://github.com/AgentComputerAI/torch --skill contributing-agentcomputerai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contributing
Source: https://github.com/AgentComputerAI/torch/tree/main/skills/contributing
Command: npx skills add https://github.com/AgentComputerAI/torch --skill contributing-agentcomputerai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides clear, step‑by‑step guidance for contributors who want to submit pull requests, add new site skills, or improve existing torch documentation, ensuring consistent quality and reducing onboarding friction.

Core Features & Use Cases

Contribution workflow: Complete PR process from branch naming to description requirements.
Skill authoring standards: Rules for naming, frontmatter, and directory layout for new site or core skills.
Quality checklist: Validation steps before opening a PR, including code build and linting.
Use cases: Adding a new site scraper, updating a selector, fixing documentation, or enhancing core tooling.

Quick Start

Ask the agent to show the contribution guide for adding a new site skill.

Frequently Asked Questions about contributing

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

FAQPage Schema

What is the standard workflow for submitting a pull request to add new torch skills?▼

The standard pull request workflow for new torch skills requires specific branch naming conventions, structured PR descriptions, and adherence to skill authoring standards before review. Contributors follow these guidelines to ensure consistent documentation and reduce onboarding friction during the merging process.

How do I author a new site skill and structure its directory layout?▼

To author a new site skill, you must follow specific naming rules, configure the required frontmatter, and organize files according to the established directory layout. These skill authoring conventions ensure your scraper or selector integrates properly with the existing torch documentation and core tooling.

What quality checklist items need validation before opening a pull request?▼

Before opening a pull request, the quality checklist requires validating code builds, running linting checks, and verifying version bumping compliance. Completing these validation steps ensures your new site skills or documentation updates meet the necessary standards for merging into the core repository.

Does contributing to torch skills require specific version bumping and documentation updates?▼

Yes, contributing to torch skills requires version bumping and consistent documentation updates within your pull request. Maintainers enforce these requirements to guarantee that new site skills, selector fixes, and core tooling enhancements remain traceable and meet quality standards before final approval.

Can I use this workflow to update an existing site scraper or fix documentation?▼

Yes, you can use this contribution workflow to update existing site scrapers, modify selectors, or fix torch documentation. The process provides complete guidance for PR naming, description formatting, and quality compliance regardless of whether the task involves core tooling enhancements or documentation fixes.

When should I not use the standard pull request workflow for torch skill contributions?▼

You should not bypass the standard pull request workflow when making minor documentation fixes or large core tooling updates to torch skills. Skipping the quality checklist, version bumping, or required PR descriptions increases onboarding friction and risks rejection during the maintainer review process.