{"owner":"aden-hive","repo":"hive","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Guidelines\n\nShared agent instructions for this workspace.\n\n## Coding Agent Notes\n\n- \n- When working on a GitHub Issue or PR, print the full URL at the end of the task.\n- When answering questions, respond with high-confidence answers only: verify in code; do not guess.\n- Do not update dependencies casually. Version bumps, patched dependencies, overrides, or vendored dependency changes require explicit approval.\n- Add brief comments for tricky logic. Keep files reasonably small when practical; split or refactor large files instead of growing them indefinitely.\n- If shared guardrails are available locally, review them; otherwise follow this repo's guidance.\n- Use `uv` for Python execution and package management. Do not use `python` or `python3` directly unless the user explicitly asks for it.\n- Prefer `uv run` for scripts and tests, and `uv pip` for package operations.\n\n\n## Multi-Agent Safety\n\n- Do not create, apply, or drop `git stash` entries unless explicitly requested.\n- Do not create, remove, or modify `git worktree` checkouts unless explicitly requested.\n- Do not switch branches or check out a different branch unless explicitly requested.\n- When the user says `push`, you may `git pull --rebase` to integrate latest changes, but never discard other in-progress work.\n- When the user says `commit`, commit only your changes. When the user says `commit all`, commit everything in grouped chunks.\n- When you see unrecognized files or unrelated changes, keep going and focus on your scoped changes.\n\n## Change Hygiene\n\n- If staged and unstaged diffs are formatting-only, resolve them without asking.\n- If a commit or push was already requested, include formatting-only follow-up changes in that same commit when practical.\n- Only stop to ask for confirmation when changes are semantic and may alter behavior.\n"},"files":{"AGENTS.md":"# Repository Guidelines\n\nShared agent instructions for this workspace.\n\n## Coding Agent Notes\n\n- \n- When working on a GitHub Issue or PR, print the full URL at the end of the task.\n- When answering questions, respond with high-confidence answers only: verify in code; do not guess.\n- Do not update dependencies casually. Version bumps, patched dependencies, overrides, or vendored dependency changes require explicit approval.\n- Add brief comments for tricky logic. Keep files reasonably small when practical; split or refactor large files instead of growing them indefinitely.\n- If shared guardrails are available locally, review them; otherwise follow this repo's guidance.\n- Use `uv` for Python execution and package management. Do not use `python` or `python3` directly unless the user explicitly asks for it.\n- Prefer `uv run` for scripts and tests, and `uv pip` for package operations.\n\n\n## Multi-Agent Safety\n\n- Do not create, apply, or drop `git stash` entries unless explicitly requested.\n- Do not create, remove, or modify `git worktree` checkouts unless explicitly requested.\n- Do not switch branches or check out a different branch unless explicitly requested.\n- When the user says `push`, you may `git pull --rebase` to integrate latest changes, but never discard other in-progress work.\n- When the user says `commit`, commit only your changes. When the user says `commit all`, commit everything in grouped chunks.\n- When you see unrecognized files or unrelated changes, keep going and focus on your scoped changes.\n\n## Change Hygiene\n\n- If staged and unstaged diffs are formatting-only, resolve them without asking.\n- If a commit or push was already requested, include formatting-only follow-up changes in that same commit when practical.\n- Only stop to ask for confirmation when changes are semantic and may alter behavior.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Guidelines\n\nShared agent instructions for this workspace.\n\n## Coding Agent Notes\n\n- \n- When working on a GitHub Issue or PR, print the full URL at the end of the task.\n- When answering questions, respond with high-confidence answers only: verify in code; do not guess.\n- Do not update dependencies casually. Version bumps, patched dependencies, overrides, or vendored dependency changes require explicit approval.\n- Add brief comments for tricky logic. Keep files reasonably small when practical; split or refactor large files instead of growing them indefinitely.\n- If shared guardrails are available locally, review them; otherwise follow this repo's guidance.\n- Use `uv` for Python execution and package management. Do not use `python` or `python3` directly unless the user explicitly asks for it.\n- Prefer `uv run` for scripts and tests, and `uv pip` for package operations.\n\n\n## Multi-Agent Safety\n\n- Do not create, apply, or drop `git stash` entries unless explicitly requested.\n- Do not create, remove, or modify `git worktree` checkouts unless explicitly requested.\n- Do not switch branches or check out a different branch unless explicitly requested.\n- When the user says `push`, you may `git pull --rebase` to integrate latest changes, but never discard other in-progress work.\n- When the user says `commit`, commit only your changes. When the user says `commit all`, commit everything in grouped chunks.\n- When you see unrecognized files or unrelated changes, keep going and focus on your scoped changes.\n\n## Change Hygiene\n\n- If staged and unstaged diffs are formatting-only, resolve them without asking.\n- If a commit or push was already requested, include formatting-only follow-up changes in that same commit when practical.\n- Only stop to ask for confirmation when changes are semantic and may alter behavior.\n","category":"root","tokens":460}]}