commit

Engineering Community

Skill notes

Step 1: Understand the Changes

Run in parallel:

Step 2: Generate Commit Message

Write a conventional commit message in Norwegian: Format: type: kort beskrivelse — types: feat fix chore test docs refactor a11y One short line on the "why"; use — for multi-concern: fix: småfiks — typo, typesikkerhet m.m. Present message and ask for confirmation before proceeding.

Step 3: Stage Files

Stage only files relevant to this task. Unstage unrelated files first (git restore --staged <file>). Never stage: .env*, credentials, node_modules/, coverage/. Use git add <specific-file> — never git add -A or git add ..

Step 4.5: Code Review Before Push

Skip if push was NOT requested. This step loops until the review is clean, max 3 iterations. Track iteration count starting at 1. Dispatch a general-purpose Agent with this prompt (fill placeholders): You are a Senior Code Reviewer. What Was Implemented

Step 5: Push (Only If Requested)

NEVER use git push. Always:

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
Plug-and-play
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
  • 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: Understand the Changes

Run in parallel:

02
Step 2: Generate Commit Message

Write a conventional commit message in Norwegian: Format: `type: kort beskrivelse` — types: `feat` `fix` `chore` `test` `docs` `refactor` `a11y` One short line on the "why"; use `—` for multi-concern: `fix: småfiks — typo, typesikkerhet m.m.` Present message and ask for confirmation before proceeding.

03
Step 3: Stage Files

Stage only files relevant to this task. Unstage unrelated files first (`git restore --staged <file>`). Never stage: `.env*`, credentials, `node_modules/`, `coverage/`. Use `git add <specific-file>` — never `git add -A` or `git add .`.

04
Step 4: Create the Commit

Step 4: Create the Commit

05
Step 4.5: Code Review Before Push

Skip if push was NOT requested. This step loops until the review is clean, max 3 iterations. Track iteration count starting at 1. Dispatch a `general-purpose` Agent with this prompt (fill placeholders): You are a Senior Code Reviewer. What Was Implemented

06
Step 5: Push (Only If Requested)

NEVER use `git push`. Always:

07
Step 6: Report

One-line summary: commit message, files changed, pushed or not. Source: ahaarrestad/tennerogtrivsel_new — distributed by TomeVault.

Discussion

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