git-and-githublisted

# GitHub Workflow Use `git` for repository operations (clone, fetch, commit, push, branch, merge). Use GitHub MCP for GitHub-specific operations (PRs, issues, releases, Actions, checks). **Tooling**: Prefer GitHub MCP server tools (`mcp__plugin_claudius_github__*`) for all GitHub API operations -- PRs, issues, reviews, actions, branches, releases, security alerts. If GitHub MCP is unavailable, read [gh-cli-fallback.md](references/gh-cli-fallback.md) for `gh` CLI equivalents. **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 work already in progress. ## 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 message format (always use HEREDOC): ```bash git add <file1> <file2> git commit -m "$(cat <<'EOF' <type>: <description> <optional body> Co-Authored-By: Clau