Rules

Documentation should be created and kept in source control ONLY if it meets these criteria:

**MANDATORY FOR ALL AI AGENTS**: After making ANY changes to files in this repository, you MUST: 1. **Stage all modified files**: `git add <file1> <file2> ...` (or `git add .` for all changes) 2. **Commit with a descriptive message**: `git commit -m "type: descriptive message"`

This workspace contains TWO independent git repositories cloned as siblings: Both repos are .gitignored from this workspace root. Commits and PRs go to their own upstream repos, not here.

<type>: <description> Types: feat, fix, refactor, docs, test, chore, perf, ci Note: Attribution disabled globally via ~/.claude/settings.json.

Thread-based version control for conversational coding. Wraps git, treating conversation threads as the primary unit of change.

This is the master repository for curated Claude Code workflow collections.

oteam is a Python package for coordinating OpenCode agents around a shared git repo. Agents self-assign tickets, plan their work, and push changes with safety checks.

Config is inspired by LazyVim but does NOT use LazyVim directly. **Steps to upgrade:** 1. Clone LazyVim repo (if not already present): gh repo clone LazyVim/LazyVim 2. Check diff between commits to identify changes:

1. **Bump version** in `git-backup/config.yaml` 2. **Update changelog** in `git-backup/CHANGELOG.md` 3. **Commit and tag:** git commit -am "Release vX.Y.Z" git tag -a vX.Y.Z -m "Release vX.Y.Z" git push && git push --tags

1. **Minimal Dependencies:** 2. **Focus & Single Responsibility:** 6. **Git Workflow:**

When the USER says "get this up to github": 1. Run `git add .` to stage all changes 2. Run `git diff HEAD` to review changes 3. Run `git status` to check current branch 4. If on main branch, create new feature branch with format: `type/description-of-changes` by running `git checkout -b type/description-of-changes`

1. Update the issue description to reflect the latest plan. Make sure to read the latest issue description to ensure you have the latest information. Do not include outdated information in the plan. 2. Write a comment briefly summarizing the plan update. Say something like "From GitHub Copilot: Previously, [old assumption]. However, [realization]. Therefore [concise summary of updates to the plan]. [commit-sha if applicable]".