commitlisted
Install: claude install-skill stxrmik/antigravity-plus
# /commit — smart commits
**Only on the user's request, or under full access:** /commit, asking to commit in their own words («закоммить», «сохрани в git»), or full access the user granted (rules: "Full access"). That is permission to **commit**; pushing is part of /pr (or of full access when the task needs it). Otherwise, if you got here on your own, don't commit; offer it in one line instead.
## Steps
1. **Gather context** (one call, sandboxed):
```bash
bash <skill_dir>/scripts/git_context.sh commit
```
If it says "not inside a git repository", tell the user and stop.
2. **Safety gate — stop and ask** if any of these show up:
- `POSSIBLE SECRETS` or risky files (`.env`, keys, credentials) that would be committed;
- large binaries / build output / `node_modules`-like junk — suggest a `.gitignore` entry instead;
- nothing to commit → say so and stop.
3. **Decide what goes in.**
- **Other agents working here** (an `<other_agents>` block before your step, or
`python3 "<skill_dir>/../../hooks/coord.py" status --workspace "<ws>"` lists someone): commit only your own files,
`python3 "<skill_dir>/../../hooks/coord.py" mine --conversation <your id> --workspace "<ws>"`. Leave theirs alone.
- If something is already staged, commit **only the staged changes** unless the user asked for "everything".
- If nothing is staged, stage the relevant changes by **explicit paths** (`git add <paths>`), never blind `git add -A` when untracked junk exists