git branch --show-current

git fetch --all --prune
git pull --ff-only

git status --porcelain

undefined

For **ambiguous** untracked paths (not obviously an artifact), ask the user before adding.

Stage and commit `.gitignore` changes as a standalone commit:

```text
chore: update .gitignore — exclude build artifacts and env files

undefined

undefined

undefined

undefined

chore(deps): fix [critical|high] security vulnerabilities — <brief description>

undefined

Count the number of files that would be reformatted.

**If count > threshold (default: 10):**

> 🛑 **Formatting check found N files that would be reformatted.**
> Creating a dedicated formatting commit before implementing your task has these benefits:
> * **Clean diffs** — reviewers see only your feature changes, not whitespace noise
> * **Clearer Git history** — formatting is a separate, revertable concern
> * **Easier code review** — no mixing of stylistic and semantic changes
> * **Reduced merge conflicts** — formatting is settled before feature branching
> 
> 
> **Would you like to:**
> 1. Apply formatting now in a dedicated commit, then proceed with your task
> 2. Skip formatting for now and proceed directly with the task
> 3. Apply formatting only to files touched by the task (post-coding)
> 
> 

Store the user's choice for future sessions.

undefined

Classify output:

| Violation Count | Classification | Action |
| --- | --- | --- |
| 0–5 | Minor | Continue, note in output |
| 6–20 | Moderate | Stop, ask user (fix in dedicated commit or continue?) |
| 21+ | Extensive | Stop, strongly recommend dedicated lint fix commit |

If user chooses to fix lint:

1. Run auto-fix where safe: `npx eslint . --fix`, `ruff check . --fix`, `cargo clippy --fix`
2. Manually address remaining issues
3. Commit:
```text
chore(lint): resolve linting violations before feature work

ls .github/workflows/     # GitHub Actions
ls .gitlab-ci.yml         # GitLab CI
ls Jenkinsfile            # Jenkins
ls .circleci/config.yml   # CircleCI
ls .travis.yml            # Travis CI
ls azure-pipelines.yml    # Azure DevOps
ls bitbucket-pipelines.yml
ls .drone.yml

undefined

**Example mapping (GitHub Actions → local equivalents):**

```yaml

For each detected CI step, run it locally and capture exit codes. If any step fails:

> ⚠️ **CI pre-validation failure: `<step name>**`
> The following CI step failed locally: `<command>`
> Exit code: `<N>`
> Output: `<last 20 lines>`
> This will likely cause CI to fail after push.
> **Would you like to:**
> 1. Fix the issue now before implementing the task
> 2. Note it and proceed (I'll flag this again at post-coding validation)
> 3. Abort
> 
>

ls .git/hooks/pre-commit .git/hooks/pre-push
ls .husky/pre-commit .husky/pre-push            # Husky
ls .lefthook.yml lefthook.yml                   # Lefthook
ls .pre-commit-config.yaml                      # pre-commit framework

undefined

If hooks fail, stop and report. Hooks represent the project's own quality gate — do not bypass them.

---

undefined

git stash         # if not yet committed

undefined

Present this to the user and ask for confirmation before proceeding.

git tag pre-refactor/<task-slug>-$(date +%Y%m%d)
git push origin pre-refactor/<task-slug>-$(date +%Y%m%d)

skip_pre_coding_format: <true|false>
skip_pre_coding_lint: <true|false>
format_commit_threshold: <N>
audit_severity_threshold: <critical|high|moderate>

Task:   <one-line description of what is being implemented>
Files:  <exhaustive list of files to modify>
Scope:  <what is explicitly OUT of scope for this change>

undefined

undefined

git diff --name-only | xargs npx eslint --fix
git diff --name-only | xargs ruff check --fix

npx tsc --noEmit                    # TypeScript
mypy <changed_files>                # Python
cargo check                         # Rust
go vet ./...                        # Go

undefined

undefined

undefined

undefined

npm run build
cargo build --release
go build ./...
python -m build
mvn package -q

pre-commit run --files $(git diff --name-only)
bash .git/hooks/pre-commit

undefined

undefined

ls CHANGELOG.md CHANGELOG.rst CHANGELOG.txt CHANGES.md HISTORY.md RELEASES.md 2>/dev/null

undefined

If user confirms an entry is needed, add it and stage `CHANGELOG.md` alongside the feature files in the same commit (not a separate commit — changelog belongs with the change).

---

git status
git diff --stat

git stash       # stash unstaged
git diff --cached | gitleaks detect --no-git --pipe
git stash pop   # restore unstaged

git add <file1> <file2> ...    # Always stage explicitly, never `git add .`
git diff --cached --stat       # Confirm staged set looks correct

<type>(<scope>): <short imperative summary>

<Paragraph explaining WHY the change was made and WHAT problem it solves.
Wrap at 72 characters. Use present tense. Be specific — avoid "fix bug".>

<Optional paragraph for architectural impact, migration steps, or
behavioral changes users/consumers should be aware of.>

Refs: #<issue>, #<pr>
Breaking-Change: <description if applicable>

git push origin <branch>

gh pr create \
  --title "<commit summary>" \
  --body "<commit body>" \
  --base main \
  --head <current-branch> \
  --draft  # Ask user: Draft or Ready?

glab mr create \
  --title "<commit summary>" \
  --description "<commit body>" \
  --source-branch <current-branch>

1. chore: update .gitignore                      (if needed)
2. chore(deps): fix security vulnerabilities     (if audit findings patched)
3. style: apply formatter to codebase            (if user approved pre-coding format)
4. chore(lint): resolve linting violations       (if user approved pre-coding lint)
5. feat/fix/refactor(<scope>): <main task>       (the actual work + changelog + tests)