{"owner":"fujiapple852","repo":"trippy","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Trippy Agent Guidelines\n\nThis repository follows the guidance below when making changes.\n\n## Development commands\n\n- Check the code with `cargo check --workspace --all-features --tests`.\n- Test the code with `cargo test`. Do not pass `--all-features`.\n- Format Rust code with `cargo fmt --all`.\n- Format non-Rust code with `dprint fmt` (install with `cargo install --locked dprint`).\n- Lint with `cargo clippy --workspace --all-features --tests -- -Dwarnings`.\n- If CLI arguments, man pages or shell completions change, update snapshots:\n  `cargo test && cargo insta review`.\n- If the `Dockerfile` changes, build it locally using `docker build . -t trippy:dev`.\n\n## Commit messages\n\n- Use the Conventional Commits format:\n  `<type>[optional scope]: <description>` where `<type>` is one of\n  `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `test`, `build`, `ci`, or `revert`.\n- For code changes set the scope to one of `core`, `dns`, `packet`, `privilege` or `tui`.\n- Use backquotes for file names and code items in the description.\n- For documentation fixes use `docs: fix <description>`.\n- Prefer small, focused commits. For larger changes, use multiple commits with clear messages.\n\n## Recommendations\n\n- Run test, format and clippy before submitting a pull request and ensure all CI checks pass.\n- Keep documentation and examples in sync with code changes.\n- Use feature branches for separate tasks.\n- Open issues and pull requests through GitHub for discussion and review.\n- Always rebase your branch before when editing an open pull request to keep the history clean.\n"},"files":{"AGENTS.md":"# Trippy Agent Guidelines\n\nThis repository follows the guidance below when making changes.\n\n## Development commands\n\n- Check the code with `cargo check --workspace --all-features --tests`.\n- Test the code with `cargo test`. Do not pass `--all-features`.\n- Format Rust code with `cargo fmt --all`.\n- Format non-Rust code with `dprint fmt` (install with `cargo install --locked dprint`).\n- Lint with `cargo clippy --workspace --all-features --tests -- -Dwarnings`.\n- If CLI arguments, man pages or shell completions change, update snapshots:\n  `cargo test && cargo insta review`.\n- If the `Dockerfile` changes, build it locally using `docker build . -t trippy:dev`.\n\n## Commit messages\n\n- Use the Conventional Commits format:\n  `<type>[optional scope]: <description>` where `<type>` is one of\n  `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `test`, `build`, `ci`, or `revert`.\n- For code changes set the scope to one of `core`, `dns`, `packet`, `privilege` or `tui`.\n- Use backquotes for file names and code items in the description.\n- For documentation fixes use `docs: fix <description>`.\n- Prefer small, focused commits. For larger changes, use multiple commits with clear messages.\n\n## Recommendations\n\n- Run test, format and clippy before submitting a pull request and ensure all CI checks pass.\n- Keep documentation and examples in sync with code changes.\n- Use feature branches for separate tasks.\n- Open issues and pull requests through GitHub for discussion and review.\n- Always rebase your branch before when editing an open pull request to keep the history clean.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Trippy Agent Guidelines\n\nThis repository follows the guidance below when making changes.\n\n## Development commands\n\n- Check the code with `cargo check --workspace --all-features --tests`.\n- Test the code with `cargo test`. Do not pass `--all-features`.\n- Format Rust code with `cargo fmt --all`.\n- Format non-Rust code with `dprint fmt` (install with `cargo install --locked dprint`).\n- Lint with `cargo clippy --workspace --all-features --tests -- -Dwarnings`.\n- If CLI arguments, man pages or shell completions change, update snapshots:\n  `cargo test && cargo insta review`.\n- If the `Dockerfile` changes, build it locally using `docker build . -t trippy:dev`.\n\n## Commit messages\n\n- Use the Conventional Commits format:\n  `<type>[optional scope]: <description>` where `<type>` is one of\n  `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `test`, `build`, `ci`, or `revert`.\n- For code changes set the scope to one of `core`, `dns`, `packet`, `privilege` or `tui`.\n- Use backquotes for file names and code items in the description.\n- For documentation fixes use `docs: fix <description>`.\n- Prefer small, focused commits. For larger changes, use multiple commits with clear messages.\n\n## Recommendations\n\n- Run test, format and clippy before submitting a pull request and ensure all CI checks pass.\n- Keep documentation and examples in sync with code changes.\n- Use feature branches for separate tasks.\n- Open issues and pull requests through GitHub for discussion and review.\n- Always rebase your branch before when editing an open pull request to keep the history clean.\n","category":"root","tokens":395}]}