pr-fix-build

To automatically apply ESLint and Prettier formatting to a remote pull request branch, you can use a skill that targets the specified branch and executes code formatting fixes directly. It requires the gh and git CLI tools along with existing node_modules.

Yes, you can run automated tests and formatting on a GitHub branch without manual intervention by executing a skill that applies fixes to the specified remote branch. It processes tasks like ESLint checks and automated testing directly.

Yes, you need node_modules installed at the root of the main repository to run automated code fixes. The process relies on local ESLint and Prettier installations, alongside the gh and git CLI tools, to apply changes.

The best way to ensure remote pull requests meet coding standards automatically is to apply a skill that executes ESLint and Prettier on the specified branch. This enforces coding standards and passes tests without manual intervention.

Automated branch formatting fails to find the ESLint configuration because it requires node_modules to be present at the root of the main repository. Ensure the gh and git CLI tools are installed and the repository dependencies are fully installed.

Yes, you can choose between fixing formatting or tests when targeting a pull request branch. The skill accepts a fix option parameter, allowing you to specify either format for Prettier and ESLint or tests for automated testing.