chore

Standardize non-TDD chore edits with mandatory archive, memory-flush, and commit steps.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill chore-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chore
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/chore
Command: npx skills add https://github.com/friedbotstudio/baseline --skill chore-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chore work still needs a disciplined workflow so documentation, configuration, and vendored-skill edits do not drift outside the baseline rules.

Core Features & Use Cases

  • Handles non-TDD changes such as README updates, typo fixes, configuration tweaks, dependency bumps, and skill content refreshes.
  • Preserves governance by enforcing archive, memory-flush, and commit steps while running verify, simplify, integrate, or document only when their triggers apply.
  • Useful when you need to update counts, rename paths, or adjust prose without forcing a failing-test loop that does not fit the task.

Quick Start

Use the chore skill to update the requested documentation or configuration files while following its mandatory archive, memory-flush, and commit workflow.

Frequently Asked Questions about chore

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

FAQPage Schema
How do I update documentation without forcing a TDD workflow?

To update documentation without a TDD workflow, apply a chore workflow that standardizes direct edits for README updates, typo fixes, and configuration tweaks while skipping failing-test loops. It enforces mandatory archive, memory-flush, and commit steps to preserve governance.

What is a chore workflow for non-TDD configuration changes?

A chore workflow for non-TDD configuration changes is a standardized process that applies direct edits to configuration tweaks, dependency bumps, and formatting fixes while enforcing mandatory archive, memory-flush, and commit gates to maintain baseline governance.

How do I manage vendored-skill updates and dependency bumps in a Claude Code repository?

Manage vendored-skill updates and dependency bumps by running a non-TDD chore workflow that requires direct edits, conditional phase selection, and commit-ready workflow state tracking without skipping mandatory archive and memory-flush gates.

When should I use a non-TDD chore workflow instead of a failing-test loop?

Use a non-TDD chore workflow instead of a failing-test loop when handling documentation edits, configuration tweaks, renaming paths, or adjusting prose that do not fit a forced failing-test cycle but still need disciplined execution and governance.

Does the chore workflow require running verify, simplify, and document phases for every configuration tweak?

The chore workflow does not require running verify, simplify, and document phases for every configuration tweak; it conditionally selects these phases only when their specific triggers apply, while always enforcing archive, memory-flush, and commit steps.