{"owner":"wfxr","repo":"forgit","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"Repository Guidelines\n=====================\n\nProject Structure & Module Organization\n---------------------------------------\n\n`forgit` is a shell-based Git helper, so most changes land in a small set of files:\n\n- `bin/git-forgit`: core command implementations and shared helper functions.\n- `forgit.plugin.zsh`: main plugin entry point for Zsh and Bash. `forgit.plugin.sh` is a symlink to it.\n- `conf.d/forgit.plugin.fish`: Fish integration.\n- `completions/`: shell completion files for Zsh, Bash, and Fish.\n- `tests/*.test.sh`: Bashunit coverage for helpers and command behavior.\n- `README.md` and `CONTRIBUTING.md`: user-facing docs and contributor workflow notes.\n\nWhen you add or rename a command, update the implementation, shell wrappers, completions, tests, and docs together.\n\nBuild, Test, and Development Commands\n-------------------------------------\n\nThere is no build step; validation is command-driven.\n\n- `shellcheck forgit.plugin.sh bin/git-forgit`: lint the shared shell sources.\n- `lib/bashunit .`: run the full test suite in `tests/`.\n- `bash forgit.plugin.sh`: verify Bash compatibility.\n- `zsh forgit.plugin.zsh`: verify Zsh compatibility.\n- `fish conf.d/forgit.plugin.fish`: verify Fish compatibility.\n- `rumdl check .`\n\nCI runs these checks on macOS and Ubuntu. Keep local validation aligned with that workflow before opening a PR.\n\nCoding Style & Naming Conventions\n---------------------------------\n\nFollow `.editorconfig`: UTF-8, LF endings, spaces for indentation, width 4, and no trailing whitespace.\nMatch the existing shell style: prefer small helper functions, `local` variables inside functions,\nand descriptive private names such as `_forgit_extract_branch_name`.\nKeep command aliases and completion names consistent across shells.\n\nTesting Guidelines\n------------------\n\nTests use Bashunit and live in `tests/*.test.sh`.\nName new files after the behavior under test, such as `worktree.test.sh` or `checkout.test.sh`.\nSource `bin/git-forgit` in tests and exercise helpers directly when possible.\nAdd or update tests for behavior changes, especially parsing, selection, and cross-shell integration.\n\nCommit & Pull Request Guidelines\n--------------------------------\n\nGit history follows Conventional Commits: `feat: ...`, `fix: ...`, `docs: ...`, `refactor: ...`,\nand occasional scoped forms like `style(docs): ...`.\nWrite messages around the behavior change and its reason, not just the implementation detail.\n\nUse the PR template.\nBefore submitting, perform a self-review, update docs for user-visible changes, add tests when behavior changes,\nand report the shells and operating systems you verified.\n"},"files":{"AGENTS.md":"Repository Guidelines\n=====================\n\nProject Structure & Module Organization\n---------------------------------------\n\n`forgit` is a shell-based Git helper, so most changes land in a small set of files:\n\n- `bin/git-forgit`: core command implementations and shared helper functions.\n- `forgit.plugin.zsh`: main plugin entry point for Zsh and Bash. `forgit.plugin.sh` is a symlink to it.\n- `conf.d/forgit.plugin.fish`: Fish integration.\n- `completions/`: shell completion files for Zsh, Bash, and Fish.\n- `tests/*.test.sh`: Bashunit coverage for helpers and command behavior.\n- `README.md` and `CONTRIBUTING.md`: user-facing docs and contributor workflow notes.\n\nWhen you add or rename a command, update the implementation, shell wrappers, completions, tests, and docs together.\n\nBuild, Test, and Development Commands\n-------------------------------------\n\nThere is no build step; validation is command-driven.\n\n- `shellcheck forgit.plugin.sh bin/git-forgit`: lint the shared shell sources.\n- `lib/bashunit .`: run the full test suite in `tests/`.\n- `bash forgit.plugin.sh`: verify Bash compatibility.\n- `zsh forgit.plugin.zsh`: verify Zsh compatibility.\n- `fish conf.d/forgit.plugin.fish`: verify Fish compatibility.\n- `rumdl check .`\n\nCI runs these checks on macOS and Ubuntu. Keep local validation aligned with that workflow before opening a PR.\n\nCoding Style & Naming Conventions\n---------------------------------\n\nFollow `.editorconfig`: UTF-8, LF endings, spaces for indentation, width 4, and no trailing whitespace.\nMatch the existing shell style: prefer small helper functions, `local` variables inside functions,\nand descriptive private names such as `_forgit_extract_branch_name`.\nKeep command aliases and completion names consistent across shells.\n\nTesting Guidelines\n------------------\n\nTests use Bashunit and live in `tests/*.test.sh`.\nName new files after the behavior under test, such as `worktree.test.sh` or `checkout.test.sh`.\nSource `bin/git-forgit` in tests and exercise helpers directly when possible.\nAdd or update tests for behavior changes, especially parsing, selection, and cross-shell integration.\n\nCommit & Pull Request Guidelines\n--------------------------------\n\nGit history follows Conventional Commits: `feat: ...`, `fix: ...`, `docs: ...`, `refactor: ...`,\nand occasional scoped forms like `style(docs): ...`.\nWrite messages around the behavior change and its reason, not just the implementation detail.\n\nUse the PR template.\nBefore submitting, perform a self-review, update docs for user-visible changes, add tests when behavior changes,\nand report the shells and operating systems you verified.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"Repository Guidelines\n=====================\n\nProject Structure & Module Organization\n---------------------------------------\n\n`forgit` is a shell-based Git helper, so most changes land in a small set of files:\n\n- `bin/git-forgit`: core command implementations and shared helper functions.\n- `forgit.plugin.zsh`: main plugin entry point for Zsh and Bash. `forgit.plugin.sh` is a symlink to it.\n- `conf.d/forgit.plugin.fish`: Fish integration.\n- `completions/`: shell completion files for Zsh, Bash, and Fish.\n- `tests/*.test.sh`: Bashunit coverage for helpers and command behavior.\n- `README.md` and `CONTRIBUTING.md`: user-facing docs and contributor workflow notes.\n\nWhen you add or rename a command, update the implementation, shell wrappers, completions, tests, and docs together.\n\nBuild, Test, and Development Commands\n-------------------------------------\n\nThere is no build step; validation is command-driven.\n\n- `shellcheck forgit.plugin.sh bin/git-forgit`: lint the shared shell sources.\n- `lib/bashunit .`: run the full test suite in `tests/`.\n- `bash forgit.plugin.sh`: verify Bash compatibility.\n- `zsh forgit.plugin.zsh`: verify Zsh compatibility.\n- `fish conf.d/forgit.plugin.fish`: verify Fish compatibility.\n- `rumdl check .`\n\nCI runs these checks on macOS and Ubuntu. Keep local validation aligned with that workflow before opening a PR.\n\nCoding Style & Naming Conventions\n---------------------------------\n\nFollow `.editorconfig`: UTF-8, LF endings, spaces for indentation, width 4, and no trailing whitespace.\nMatch the existing shell style: prefer small helper functions, `local` variables inside functions,\nand descriptive private names such as `_forgit_extract_branch_name`.\nKeep command aliases and completion names consistent across shells.\n\nTesting Guidelines\n------------------\n\nTests use Bashunit and live in `tests/*.test.sh`.\nName new files after the behavior under test, such as `worktree.test.sh` or `checkout.test.sh`.\nSource `bin/git-forgit` in tests and exercise helpers directly when possible.\nAdd or update tests for behavior changes, especially parsing, selection, and cross-shell integration.\n\nCommit & Pull Request Guidelines\n--------------------------------\n\nGit history follows Conventional Commits: `feat: ...`, `fix: ...`, `docs: ...`, `refactor: ...`,\nand occasional scoped forms like `style(docs): ...`.\nWrite messages around the behavior change and its reason, not just the implementation detail.\n\nUse the PR template.\nBefore submitting, perform a self-review, update docs for user-visible changes, add tests when behavior changes,\nand report the shells and operating systems you verified.\n","category":"root","tokens":659}]}