task-workflow

Automate the GitHub pull request workflow by using a skill that creates an issue, branches, implements changes, runs verification tooling, and opens a PR with conventional commits and changelog updates. This ensures consistent project hygiene.

Enforce quality gates like ruff and mypy before opening a pull request by running formatting, linting, type checking, and unit tests as strict non-skipping verification steps that block commit creation on failures.

An automated task workflow handles branching and issue creation by creating a GitHub issue for the specific task, branching appropriately, implementing changes, and preparing a pull request with a clear summary and test plan.

Yes, you can use this workflow for documentation and refactoring tasks. It applies to feature, bugfix, refactor, test, and documentation work, requiring ordered execution of steps, conventional commit formatting, and changelog updates.

Your pull request workflow requires running unittest discovery and type checking to enforce quality gates before merging. Strict non-skipping of verification ensures formatting, linting, type checking, and unit tests pass before PR creation.

No, you do not need to manually update the changelog. The automated GitHub workflow enforces changelog updates and conventional commit messaging tied to the created issue, ensuring process-aligned project hygiene.