git-and-githublisted

# GitHub Workflow **Tooling**: `git` for repository operations; `gh` CLI and the `scripts/gh-*.sh` wrappers for all GitHub API operations (PRs, issues, reviews, Actions, checks, branches, releases, security alerts) — see [gh-cli.md](references/gh-cli.md). **Attribution**: every commit, PR, issue, and comment posted to GitHub **must** include this footer (blank line before it): ``` <sub>🤖 Co-authored by [Claudius the Magnificent](https://github.com/lklimek/claudius) AI Agent</sub> ``` ## Before Starting Work 1. Verify you're on a base branch — if on an unrelated feature branch, switch to base or confirm with user. 2. Pull (fast-forward only). On diverged history, rebase if trivial, otherwise alert user. 3. Search open PRs for related fixes — don't duplicate in-progress work. ## Committing Create feature branches. NEVER commit to base branch. Stage specific files — never `git add .` or `git add -A`. Use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) (`feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`); append `!` for breaking changes. Commit format (always HEREDOC). Substitute `<your-model-name>` with your actual current model — never copy a version literally from this doc, it goes stale: ```bash git add <file1> <file2> git commit -m "$(cat <<'EOF' <type>: <description> <optional body> Co-Authored-By: Claude <your-model-name> <noreply@anthropic.com> EOF )" ``` ## Changelog Edit `CHANGELOG.md` per [Keep a Changelog](https:/