commit
- Repo stars 1,209
- License Apache-2.0
- Author repo oasdiff
- 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.
## 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.
Sections and files
Listed in source order.
sections -> Git workflow
terms -> NEVER push directly to main. · 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.
files/cmd -> make lint · feature/fix
body sha256 -> 413b65c6ce01
Git workflow
NEVER push directly to main. Always: Create a feature/fix branch Commit changes there Push the branch Open a PR