mike/Housekeeping
Watch
1
0
Fork
You've already forked Housekeeping
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A place to organize things that need to get done that have an impact on all projects and or daily life that need to be worked on.
1 commit 1 branch 0 tags 25 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
claude-bot 2020777877 Scaffold housekeeping tracker 
README: purpose, in/out-of-scope, workflow, and label taxonomy.
Issue template: what / why defer / what it'd take / risks / DoD.
Labels seeded separately via Forgejo API.
2026-04-20 10:02:16 -04:00
.forgejo/issue_template Scaffold housekeeping tracker 2026-04-20 10:02:16 -04:00
README.md Scaffold housekeeping tracker 2026-04-20 10:02:16 -04:00

README.md

Housekeeping

A dumping ground for cross-project cleanup items, tooling reorganization, and operational TODOs that don't belong in any single project's issue tracker.

What goes here

Anything that:

  • Touches infrastructure shared across multiple projects (MCPs, dotfiles, dev environment, shell setup)
  • Is cosmetic or organizational rather than feature-driven
  • Would feel out-of-scope in a focused project repo (Minerva, Legislation_Tracker, etc.)
  • Is a repeatable operational task ("rotate X", "audit Y", "archive old Z")

What does NOT go here

  • Project-specific bugs, features, or PRD work → owning project's tracker
  • Time-sensitive incidents → handled in the moment, not queued here
  • Long-form plans or PRDs → live in the project that owns them

Workflow

Housekeeping is a low-ceremony tracker. No sprints, no SLAs, no prioritization discipline beyond the labels below.

  1. When something surfaces during real work (usually "we should reorganize X later"), open an issue here and move on.
  2. Write the issue body as a full brief using the template — future-you picks it up cold and shouldn't have to reconstruct context.
  3. Label the area. Priority defaults to unlabelled (medium); use priority/high for actively-degrading items, priority/low for purely cosmetic.
  4. On a housekeeping day, triage the backlog and knock items out in a focused sitting.

Labels

Area — what kind of cleanup

  • area/tooling — MCPs, CLI tools, editors, developer UX
  • area/infra — servers, Docker, deploy paths, networking, backups
  • area/dotfiles — Claude settings, shell config, git config, keybindings
  • area/process — workflows, conventions, documentation habits
  • area/daily-life — non-code operational tasks (account cleanup, subscriptions)

Priority — optional

  • priority/high — actively blocking or degrading something
  • priority/low — purely cosmetic, can sit indefinitely

Status — optional

  • status/blocked — waiting on something external (vendor, hardware, upstream decision)

Unlabelled items are assumed ready-to-pick-up at medium priority.

Issue template

New issues use a brief format covering: what, why deferred, what it would take, risks, and definition of done. Located at .forgejo/issue_template/housekeeping.md. If an item isn't worth filling that out, it probably doesn't need a tracker entry.