pr
- Repo stars 6,503
- License Apache-2.0
- Author repo plano
- 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
- @katanemo · 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.
Create a pull request for the current changes:
1. Determine the GitHub username via `gh api user --jq .login`. If the login is `adilhafeez`, use `adil` instead.
2. Create a feature branch using format `<username>/<feature_name>` — infer the feature name from the changes
3. Run `cd crates && cargo fmt --all -- --check` and `cd crates && cargo clippy --locked --all-targets --all-features -- -D warnings` to verify Rust code is clean
4. Commit all changes with a short, concise commit message (one line, no Co-Authored-By)
5. Push the branch and create a PR targeting `main`
Keep the PR title short (under 70 chars). Include a brief summary in the body. Never include a "Test plan" section or any "Generated with Claude Code" attribution.
Sections and files
Listed in source order.
sections -> → →
terms -> 1. Determine the GitHub username via gh api user --jq .login. · Keep the PR title short (under 70 chars).
files/cmd -> gh api user --jq .login · adilhafeez · adil · <username>/<feature_name> · cd crates && cargo fmt --all -- --check · cd crates && cargo clippy --locked --all-targets --all-features -- -D warnings · main
body sha256 -> 4b9c16f41c37
Determine the GitHub username via
gh api user --jq .login. If the login isadilhafeez, useadilinstead. 2. Create a feature branch using format<username>/<feature_name>— infer the feature name from the changes 3. Runcd crates && cargo fmt --all -- --checkandcd crates && cargo clippy --locked --all-targets --all-features -- -D warningsto verify Rust code is clean 4. Commit all changes with a short, concise commit message (one line, no Co-Authored-By) 5. Push the branch and create a PR targetingmain