commit

Engineering Community

Skill notes

Git workflow

NEVER push directly to main. Always: Create a feature/fix branch Commit changes there Push the branch Open a PR

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
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@oasdiff · Apache-2.0
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.

Author source file SKILL.md

## Git workflow

NEVER push directly to main. Always:
1. Create a feature/fix branch
2. Commit changes there
3. Push the branch
4. Open a PR

Before committing, run `make lint` to ensure formatting and generated files are up to date.

After the pre-commit step and staging files, write a concise commit message and commit.

Discussion

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