git push

Engineering Community

Skill notes

Step 1: Pre-flight Status

Gather context. Run ALL of these in parallel: Handle edge cases before proceeding: Detached HEAD: Stop. Tell the user to create or checkout a branch first. No remote configured: Stop. Tell the user to add a remote. On main/master with uncommitted changes: Warn and ask for confirmation before continuing.

Step 2: CI Validation

This is the ONE command that validates everything. Do not replicate its individual checks. This script covers: architecture constraints (no platform headers, no malloc in src/), clang-format, all 3 profile builds (DATA/AUDIO/MEDIA), ctest for each profile, symbol prefix validation, no global mutable state, and AddressSanitizer build+test. If it fails:

Step 3: Handle Uncommitted Changes

Only reached after Step 2 CI validation passes. If git status shows uncommitted changes (including any clang-format auto-fixes from Step 2): Show changes: Stage relevant files by name. Never stage files matching: .env*, credentials*, *.key, *.pem, *.p12. Warn the user if such files appear in the working tree.

Step 4: Patch-on-Patch Review (Advisory)

Detect layered incremental fixes in today's commits that could be squashed into cleaner history. If fewer than 2 commits today: Skip entirely. Proceed to Step 5. Look for these signals: Any .c or .h file modified in 3+ commits today (strong signal) Fix chains: "implement X" then "fix X" or "fix typo in X"

Step 5: Documentation Freshness Check (Advisory)

Compare changed files against upstream to detect potentially stale documentation. Apply these mapping rules: Changed files · Check this doc · Reason src/nano_*.c or src/nano_*.h · docs/QUALITY_SCORE.md · Module grade may need updating include/nanortc.h · ARCHITECTURE.md · Public API change affects architecture

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Pre-flight Status

Gather context. Run ALL of these in parallel: Handle edge cases before proceeding: Detached HEAD: Stop. Tell the user to create or checkout a branch first. No remote configured: Stop. Tell the user to add a remote. On main/master with uncommitted changes: Warn and ask for confirmation before continuing.

02
Step 2: CI Validation

This is the ONE command that validates everything. Do not replicate its individual checks. This script covers: architecture constraints (no platform headers, no malloc in src/), clang-format, all 3 profile builds (DATA/AUDIO/MEDIA), ctest for each profile, symbol prefix validation, no global mutable state, and AddressSanitizer build+test. If it fails:

03
Step 3: Handle Uncommitted Changes

Only reached after Step 2 CI validation passes. If `git status` shows uncommitted changes (including any clang-format auto-fixes from Step 2): Show changes: Stage relevant files by name. Never stage files matching: `.env*`, `credentials*`, `*.key`, `*.pem`, `*.p12`. Warn the user if such files appear in the working tree.

04
Step 4: Patch-on-Patch Review (Advisory)

Detect layered incremental fixes in today's commits that could be squashed into cleaner history. If fewer than 2 commits today: Skip entirely. Proceed to Step 5. Look for these signals: Any `.c` or `.h` file modified in 3+ commits today (strong signal) Fix chains: "implement X" then "fix X" or "fix typo in X"

05
Step 5: Documentation Freshness Check (Advisory)

Compare changed files against upstream to detect potentially stale documentation. Apply these mapping rules: Changed files · Check this doc · Reason `src/nano_*.c` or `src/nano_*.h` · `docs/QUALITY_SCORE.md` · Module grade may need updating `include/nanortc.h` · `ARCHITECTURE.md` · Public API change affects architecture

06
Step 6: Push

Check upstream tracking and push: No upstream: `git push -u origin $(git branch --show-current)` Has upstream: `git push`

07
Step 7: Post-push Summary

Display a summary in English: If branch is not `main`, suggest creating a PR.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.