commit

Engineering Community

Skill notes

Step 1: Run quality checks

Run all checks in parallel:

Step 2: Fix all issues

If any check fails: Lint errors: Run yarn lint:biome --fix to auto-fix, then manually fix remaining issues Type errors: Fix TypeScript errors in the affected files Formatting: Run yarn format (i.e. yarn format:check --fix) to auto-format all files Re-run the failing checks after fixing until they all pass. Do NOT proceed to commit until every check passes with zero errors.

Step 3: Create the commit

Only after all checks pass, follow the standard commit process: Run git status and git diff to review changes Stage the relevant files with git add <specific files> Write a clear commit message following the existing style Create the commit using a heredoc for the message:

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
@FezVrasta · 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
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: Run quality checks

Run all checks in parallel:

02
Step 2: Fix all issues

If any check fails: Lint errors: Run `yarn lint:biome --fix` to auto-fix, then manually fix remaining issues Type errors: Fix TypeScript errors in the affected files Formatting: Run `yarn format` (i.e. `yarn format:check --fix`) to auto-format all files Re-run the failing checks after fixing until they all pass. Do NOT proceed to commit until every check passes with zero errors.

03
Step 3: Create the commit

Only after all checks pass, follow the standard commit process: Run `git status` and `git diff` to review changes Stage the relevant files with `git add <specific files>` Write a clear commit message following the existing style Create the commit using a heredoc for the message:

Discussion

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