fastapi-grant-permissions

Grant the permissions a developer needs to work in this repo without a prompt on every routine command, while keeping sensitive files off-limits. Permissions live in your agent's config file, not in memory or preferences — this skill edits that file. It does NOT loosen anything silently: propose the allow-list, show it, then write it. ## Where your allow-list lives You're running **Cline**. Cline's auto-approval is GUI-only — there's no committed allow-list file, and `.clineignore` is the only committed control. So this skill's file-writing steps don't apply as written; tell the user that plainly, and where the agent has an equivalent control (an ignore file, a settings UI, a test/lint gate) point them at it instead of writing an allow-list. ## Steps 1. **Find the repo's real commands.** Read CLAUDE.md and any rules files first. If there's no CLAUDE.md (common on third-party repos), fall back to `README.md`, `CONTRIBUTING.md`, `package.json` `scripts`, a `Makefile`/`justfile`/`Taskfile.yml`, and a `scripts/` directory. Capture test, lint, format, type-check, build, and especially the **run/dev/start** command — that's the one people forget to allow. 2. **Detect the stack and its runner** from marker files: - `pyproject.toml` / `setup.py` → `python`, `pytest`, `ruff`, `mypy`/`pyright`, `pip`, `uv` - `package.json` → `npm`, `npx`, `node`, `yarn`, `pnpm` (read its `scripts`) - `go.mod` → `go`; `Cargo.toml` → `cargo`; `Makefile` → `make` - `docker-compose.yml` / ...