gitlisted

Execute the requested git and/or GitHub CLI operation(s) using the Bash tool. A request may combine several steps (e.g. "commit + push + pr", "commit, push") — perform each requested step in order, stopping and reporting back if any step fails. Rules: - Run `git status` (and `git diff` for commits) first to confirm what will be affected before acting. - Stage only the files the user specified or that are clearly relevant — never `git add -A` / `git add .` unless explicitly asked. - Commit messages: English, conventional-commit style (feat:, fix:, refactor:, etc.), explain why not what. - Write multi-line messages to a file and pass `git commit -F <file>`, or, in Bash, feed them on stdin behind a quoted delimiter (`git commit -F - <<'EOF'`); otherwise use repeated single-line `-m` flags in single quotes. Double quotes run anything between backticks as a command, and a message containing an apostrophe goes through `-F` instead. Never `@'...'@` — that is PowerShell here-string syntax, and in the Bash tool it leaves literal `@` characters in the message. - Never force-push, `reset --hard`, or skip hooks (`--no-verify`) unless explicitly asked. - Commit or stash before anything that discards uncommitted work — `git checkout -- <paths>`, `git restore`, a breach or mutation test that rewrites files. Restoring "to HEAD" is not undoing the last thing you did; it throws away everything since the last commit, including the fix you were checking. - Never push unless explicitly asked to