pr

Engineering Community

Skill notes

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

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
@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.

Author source file SKILL.md

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.

Discussion

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