While all of what you say rings true - it's been said before and bears repeating - git isn't a version control system as much as it is a set of version control tools from which you can design a workflow that meets your needs.
The canonical way to use git is by the git syntax. Many (most?) people don't build scripts and aliases around it. It works just fine when used raw.
However, I'm with Peaker in that losing your working copy is enough of a nuisance to deserve an interactive prompt, just like 'rm' prompts by default. Confident users could always disable the prompt with an environment-variable or .gitconfig flag.
