chore

Name: chore
Availability: InStock
Author: Bjorn

Create chore branches for non-code repository changes and open PRs via the agent dashboard.

19|2|Updated Mar 30, 2026

Search Tags:#workflow automation #conventional commits #pull requests #ci #git branching #test gating #non-code changes

Ready to run

npx skills add https://github.com/bjornjee/agent-dashboard --skill chore-bjornjee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chore
Source: https://github.com/bjornjee/agent-dashboard/tree/main/adapters/claude-code/skills/chore
Command: npx skills add https://github.com/bjornjee/agent-dashboard --skill chore-bjornjee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the risk and friction of making non-code repository changes by enforcing a consistent branch, scope validation, test run, and review/PR flow.

Core Features & Use Cases

Branch Setup for Non-Code Work: Creates a chore/<name> branch derived from your change description and ensures you are working on the correct target branch.
Scope Verification: Confirms the change is truly non-code (rules, config, docs, CI, dependency bumps) and steers you toward feature/fix skills if application logic or tests are involved.
Test and Review Gates: Runs make test when available, then performs a final convention-focused review before committing and opening a PR through the dashboard workflow.

Quick Start

Tell the agent: "Make a non-code change to update CI linting rules for our monorepo; description: adjust GitHub Actions to run the same formatter and bump the linting dependency."

Frequently Asked Questions about chore

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

FAQPage Schema

How do I automate non-code repository changes like config and CI updates?▼

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.

What's the best way to open a pull request for documentation updates 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.

Can I use this workflow to bump dependencies and adjust GitHub Actions CI pipelines?▼

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.

Why does my workflow require conventional commits for dependency bumps and config changes?▼

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.

When should I not use a chore branch for repository updates?▼

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.