Skip to content
Skills Library
Programming · Tool integration

drift-commit-push

/drift-commit-push

Drift-specific git commit and push workflow. Use when preparing commits, choosing conventional commit messages, checking pre-push gates, or deciding whether a push to main is allowed. Keywords: commit, push, git push, conventional commit, pre-push, changelog, risk audit, hooks.

Repository
drift ↗
Licence
MIT
Last repository change
30.07.2026

Assessment and security

98/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene13 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Drift-specific git commit and push workflow. Use when preparing commits, choosing conventional commit messages, checking pre-push gates, or deciding whether a push to main is allowed. Keywords: commit, push, git push, conventional commit, pre-push, changelog, risk audit, hooks.

Arguments

/drift-commit-push Describe what changed and whether you need commit help, push readiness, or both.
Original author description

Drift-specific git commit and push workflow. Use when preparing commits, choosing conventional commit messages, checking pre-push gates, or deciding whether a push to main is allowed. Keywords: commit, push, git push, conventional commit, pre-push, changelog, risk audit, hooks.

How it works

  1. When To Use
  2. Core Rules
  3. Step 0: Run The Drift Policy Gate
  4. Step 1: Classify The Change
  5. Step 2: Inspect The Working Tree
  6. Step 3: Satisfy Change-Coupled Requirements
  7. Step 4: Run Validation
  8. Step 5: Create The Commit
  9. Step 6: Evaluate Push Readiness
  10. Step 7: Push Only With Approval
Original SKILL.md headings · 196 lines, 1,016 words
SKILL.md preview
---
name: drift-commit-push
description: "Drift-specific git commit and push workflow. Use when preparing commits, choosing conventional commit messages, checking pre-push gates, or deciding whether a push to main is allowed. Keywords: commit, push, git push, conventional commit, pre-push, changelog, risk audit, hooks."
argument-hint: "Describe what changed and whether you need commit help, push readiness, or both."
---

# Drift Commit And Push Skill

Use this skill for repository-safe commit and push workflows in Drift.

## When To Use

- Prepare a commit after code changes
- Choose the correct conventional commit type
- Check whether a push is allowed
- Verify pre-push gates before pushing to `main`
- Decide which supporting artifacts must be updated with the code change

## Core Rules

1. **Do not push autonomously.** A push requires explicit maintainer approval.
2. **Never commit blocked paths.** Anything under `tagesplanung/` is excluded from pushes.
3. **Use conventional commits.** Release automation depends on `feat:`, `fix:`, and `BREAKING:` semantics.
4. **Releases are CI-automated.** Do not run manual release flows in normal operation; do not handcraft versioning beyond commit semantics.
5. **Run lightweight validation before commit; run full validation once per push cycle.**
6. **Do not bypass hooks by default.** Environment-variable bypasses are emergency-only and must be justified.

## Step 0: Run The Drift Policy Gate

Before preparing a commit or push, run the mandatory admissibility gate for the underlying task. If the task is not admissible, stop instead of committing polished but policy-invalid work.

Use the gate format from `.github/instructions/drift-policy.instructions.md`.

## Step 1: Classify The Change

Choose the commit type from the actual impact:

- `fix:` for bug fixes and regressions
- `feat:` for new user-visible capabilities
- `refactor:` for internal restructuring without behavior change
- `docs:` for documentation-only changes
- `test:` for tests-only changes
- `chore:` for maintenance work
- `BREAKING:` or a `BREAKING CHANGE:` footer for incompatible changes

If the change touches signals, scoring, output formats, or architecture boundaries, an ADR under `docs/decisions/` is required before implementation unless the change is only a bug fix or pure refactoring. Stop and satisfy that requirement before committing.

## Step 2: Inspect The Working Tree

Review exactly what will be committed:

```bash
git status --short
git diff --stat
git diff
```

Check for unrelated files and leave them out of the commit.

## Step 3: Satisfy Change-Coupled Requirements

Apply the repository gates before pushing, and usually before committing if they affect the same logical change:

- `src/drift/signals/`, `src/drift/ingestion/`, or `src/drift/output/` changed:
  update the correct audit artifacts in `audit_results/`, and keep all four audit files present.
  - Signal added or materially changed: update `fmea_matrix.md`, `fault_trees.md`, and `risk_register.md`
  - Input or output path / trust boundary changed: update `stride_threat_model.md` and `risk_register.md`
  - Precision or recall changed by more than 5 percentage points: update `fmea_matrix.md` and `risk_register.md`
- `feat:` commit planned:
  include tests, at least one empirical artifact in `benchmark_results/` or `audit_results/`, a versioned evidence file in `benchmark_results/`, and update `docs/STUDY.md` if it exists.
- `feat:` or `fix:` commit planned:
  satisfy the changelog gate. In normal operation this means including a `CHANGELOG.md` update in the push; emergency bypass requires explicit maintainer approval and reason.
- `pyproject.toml` changed:
  ensure `uv.lock` is updated too.
- New public function under `src/drift/`:
  add a docstring in the same diff if it is a lowercase `def` without a leading underscore.

Release-specific note for `src/drift/**` changes:

- Keep commit semantics correct (`feat:`, `fix:`, `BREAKING:`). CI uses python-semantic-release to derive version/tag/release.
- Do not trigger manual release commands unless CI is unavailable and maintainer explicitly requests fallback execution.

## Step 4: Run Validation

Minimum expectation before commit (fast feedback):

```bash
make test-fast
# Windows / PowerShell:
.\scripts\check.ps1 test-fast
```

For very fast local loops, prefer targeted checks first:

```bash
make test-dev
# or rerun only previous failures
make test-lf
# Windows / PowerShell equivalents:
.\scripts\check.ps1 test-dev
.\scripts\check.ps1 test-lf
```

If smoke confidence is needed locally, use the split profiles instead of always running the full matrix:

```bash
make smoke-pr
# optional full matrix
make smoke-nightly
```

Before push, the repository standard is:

```bash
# Linux / macOS / Git Bash:
make check

# Windows / PowerShell (mandatory — do NOT call make directly):
.\scripts\check.ps1
```

> **Windows agents:** `make` is not available in PowerShell. Always use `.\.scripts\check.ps1 <target>`.
> This delegates to Git Bash and writes the same SHA cache, so `git push` afterwards skips
> the expensive CI re-run inside VS Code.

Important for speed: do not duplicate full-matrix runs.

- Use exactly one full validation run per push cycle:
  - either run `make check` manually before push,
  - or rely on the pre-push hook's mandatory full checks.
- Do not run `make check` and then immediately push if the hook will rerun the same matrix anyway, unless maintainers explicitly asked for preflight output.
- For commit-only checkpoints, fast tests are sufficient; keep full validation for push readiness.

## Step 5: Create The Commit

Stage only the intended files:

```bash
git add <paths>
git commit -m "fix: concise summary"
```

Good commit subjects are:

- specific
- outcome-oriented
- scoped to one logical change

Examples:

```text
fix: prevent detached release tag lineage regressions
feat: add evidence gate for feature pushes
docs: clarify pre-push audit requirements
```

## Step 6: Evaluate Push Readiness

Before any push, confirm all of the following:

- explicit maintainer approval to push exists
- no blocked paths are included
- the relevant pre-push gates are satisfied
- full validation is green for this push cycle (either manual `make check` preflight or the pre-push hook run)
- the branch and target are intentional

Useful checks:

```bash
git diff --name-only origin/main HEAD
git log --oneline origin/main..HEAD
```

Emergency bypasses exist for individual gates, for example `DRIFT_SKIP_CHANGELOG=1`, `DRIFT_SKIP_DOCSTRING=1`, `DRIFT_SKIP_RISK_AUDIT=1`, `DRIFT_SKIP_VERSION_BUMP=1`, and `DRIFT_SKIP_LOCKFILE=1`. Use them only with explicit maintainer approval and a documented reason.

## Step 7: Push Only With Approval

If and only if approval exists:

```bash
git push origin main
```

Do not use bypasses like `DRIFT_SKIP_HOOKS=1` unless the maintainer explicitly requests an emergency override and the reason is documented.

## Review Checklist

- [ ] Commit type matches actual change impact
- [ ] Only intended files are staged
- [ ] Drift Policy Gate was satisfied for the underlying task
- [ ] Required artifacts changed together with the code
- [ ] Validation was run at the appropriate level
- [ ] Push approval was explicitly granted before pushing

## References

- `.github/copilot-instructions.md`
- `.github/instructions/drift-policy.instructions.md`
- `.github/instructions/drift-push-gates.instructions.md`
- `.github/instructions/drift-quality-workflow.instructions.md`

Versions

The database has no other skills named drift-commit-push.

Database snapshot: 13.11.2026 · package version 13403640f327 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 100git-commit
    Guide for Git commit messages and pushing code. Use when user says "commit", "push code", "push to git", "save changes to git", "git add and commit", "commit and push", or needs help writing commit messages following Conventional Commits.
  • 100git-workflow
    Conventional commits, PR creation, and quality gate verification. Use when: commit, PR, branch, push, conventional commit, create pull request, git.
  • 90commit-push
    Analyze changes, create categorized conventional commits, and push. Use when user asks to commit and push, invokes `/commit-push`, or requests conventional commits without a PR.
  • 82commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 100commit-push-pr
    Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.