rails-cto-commit
/rails-cto-commit
Dodaje do stagingu wszystkie zmiany w kodzie i tworzy commit z czytelnym komunikatem, a na życzenie wypycha go do repozytorium.
- Autor
- mattsears ↗
- Repozytorium
- rails-cto ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Dodaje do stagingu wszystkie zmiany w kodzie i tworzy commit z czytelnym komunikatem, a na życzenie wypycha go do repozytorium.
Wyzwalacze z opisu
Oryginalny opis (EN)
Stage and commit all outstanding code changes with a clear, human-friendly commit message. Use this skill whenever the user asks to commit, save their work, push changes, or says things like "commit this", "save my progress", "push this up", "ship it", "commit all", or "commit and push". Also triggers for "/commit-all". Do NOT use for cherry-picking, rebasing, or other advanced git operations.
Jak działa
- Workflow
Podgląd SKILL.md
--- name: rails-cto-commit description: Stage and commit all outstanding code changes with a clear, human-friendly commit message. Use this skill whenever the user asks to commit, save their work, push changes, or says things like "commit this", "save my progress", "push this up", "ship it", "commit all", or "commit and push". Also triggers for "/commit-all". Do NOT use for cherry-picking, rebasing, or other advanced git operations. --- # Commit Stage and commit all outstanding changes with a clear, human-friendly message. Optionally push to the remote — but only after the user confirms. ## Workflow ### 1. Gather context Run these in parallel to understand what's changed: - `git status` — see untracked and modified files - `git diff` — see unstaged changes - `git diff --cached` — see already-staged changes - `git log --oneline -5` — see recent commit style for reference If there are no changes to commit (nothing untracked, nothing modified, nothing staged), tell the user and stop. ### 2. Stage everything Add all changes — tracked and untracked — to the staging area: ```bash git add -A ``` If any files look like they contain secrets (`.env`, credentials, tokens, API keys), warn the user and exclude them before committing. ### 3. Write the commit message Write a commit message that a non-technical person could understand. The goal is clarity — someone glancing at the git log should immediately know what changed and why. **Rules:** - Use plain language. Avoid jargon, abbreviations, and technical shorthand. - Lead with what the change accomplishes from a user or product perspective, not implementation details. - Keep the subject line under 72 characters. - If the change is complex, add a blank line and a short body paragraph explaining the "why." - Do NOT include any co-authorship lines (no `Co-Authored-By`). - Do NOT reference "Claude" or any AI tool in the message. **Good examples:** - `Add password reset flow for logged-out users` - `Fix broken checkout button on mobile screens` - `Update pricing page to show annual discount` - `Remove unused admin dashboard pages` **Bad examples:** - `refactor: extract util fn for auth middleware` (too technical) - `fix bug` (too vague) - `WIP` (not descriptive) - `Update files` (says nothing) Use a HEREDOC to pass the message so multi-line messages format correctly: ```bash git commit -m "$(cat <<'EOF' Your commit subject line here Optional body explaining why, if needed. EOF )" ``` ### 4. Confirm before pushing After committing, ask the user if they want to push to the remote. Do not push automatically. If they say yes: - If the branch has no upstream, use `git push -u origin <branch>` to set tracking. - If it does, use `git push`. - Never force-push unless the user explicitly asks for it. - Warn and refuse if the target is `main` or `master` (unless the user insists). If they say no or don't mention pushing, just confirm the commit was made and stop.
Wersje
W bazie nie ma innych skilli o nazwie rails-cto-commit.
Migawka bazy z 13.11.2026 · wersja paczki aade489e7944 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 92commit
Tworzy commity w Git: stage'uje i zapisuje zmiany, a z opcją --push także wypycha je do zdalnego repozytorium. - 90git-commit-push
Zapisuje commit i wypycha bieżące zmiany do repozytorium, sprawdzając wcześniej, co trafi do historii. - 100git-commit
Zatwierdza przygotowane zmiany commitem z komunikatem w formacie conventional commit. - 100git-commit
Zatwierdza przygotowane zmiany commitem z komunikatem w formacie conventional commit. - 92commit
Zapisuje zmiany w Git przez staging i commit, a opcja --push dodatkowo wysyła je do zdalnego repozytorium. - 100git-pushing
Dodaje wszystkie zmiany, tworzy commit conventional i wypycha go na zdalną gałąź, gdy użytkownik prosi o push albo o zapis pracy na GitHubie.