Verify working-tree state and enforce staging and commit hygiene.
npx skills add https://github.com/oElberte/dotfiles --skill git-workflow-oelberte
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/oElberte/dotfiles/tree/main/private_dot_factory/skills/git-workflow Command: npx skills add https://github.com/oElberte/dotfiles --skill git-workflow-oelberte
It prevents accidental loss, leakage, and messy history by enforcing a clear, state-aware Git workflow before staging, committing, merging, or pushing.
git status --porcelain before state-dependent operations and treat untracked files as user-owned.git diff --cached and review both unstaged and staged changes before committing..env, credentials, logs, and build outputs; follow Conventional Commits; never push unless explicitly requested; use local excludes via .git/info/exclude for personal-only ignores.Use the git-workflow skill to check that what you plan to stage and commit matches your intent and includes no secrets or unintended files.
High-intent search queries and answers about installing and using this skill.
To prevent committing secrets in git, inspect staged changes with `git diff --cached` and avoid staging `.env`, credentials, logs, and build outputs. Use `.git/info/exclude` for local-only ignores to keep sensitive files untracked without modifying the shared `.gitignore`.
The safest way to stage and commit in git is to first run `git status --porcelain` to verify the working-tree state, inspect `git diff --cached` for traceability, and format messages using Conventional Commits for clear history.
Check your git working-tree state before merging or branching by running `git status --porcelain`. This verifies tracked and untracked files, treating untracked files as user-owned to prevent accidental loss during state-dependent operations.
No, a disciplined git workflow does not automatically push commits. It enforces a hard rule against pushing to the remote repository unless explicitly requested by the user, ensuring all changes are deliberate and safe.
Use local excludes via `.git/info/exclude` in git for personal-only ignores that should not be shared with the team. This prevents sensitive or environment-specific files from being tracked without modifying the repository's shared `.gitignore` file.
Strict git commit hygiene requires explicit `git status --porcelain` checks and manual review of staged changes before every commit. This deliberate workflow may slow down rapid prototyping but ensures traceable staging and prevents accidental leakage.
iludeSynchronizes ignore entries across .gitignore and .dockerignore files.
trysmrCommit current changes to a Git branch and push to the remote.
anxiety135790Scan git diffs for security risks and run baseline-aware tests before commit.
fullykubedAutomate Git commits, rebases, and squashes with safety prompts.