contributing

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.

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.

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.

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.

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.

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.