chore

Automate non-code repository changes by creating a chore branch, validating the scope, running tests, and opening a PR via the agent dashboard. This workflow ensures rules, config, docs, CI, and dependency bumps ship safely without affecting application logic.

The best way to open a PR for documentation updates is using a chore workflow that enforces branch correctness against latest main, runs make test if a Makefile exists, and opens the PR via the dashboard rather than gh directly.

Yes, you can use this workflow to bump dependencies and adjust CI pipelines because it specifically handles non-code changes. It verifies the scope steers you toward feature or fix skills if application logic or tests are involved.

Your workflow requires conventional commits for dependency bumps and config changes to enforce a consistent branch and review flow. This reduces risk and friction by performing a convention-focused review before committing and opening the PR.

You should not use a chore branch when the repository updates involve application logic or tests. The scope verification step will steer you toward feature or fix skills instead of proceeding with the chore workflow.