{"owner":"go-gitea","repo":"gitea","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"files":{"AGENTS.md":"- Never assume, verify before claiming\n- List development targets with `make help`\n- Read relevant developer documentation in the `docs` folder\n- PR descriptions: minimal, only what and why, no task or file listings. Include screenshots for UI changes, before and after when modifying existing UI. Aim for less than 1000 characters\n- Reference issues and PRs by full URL, not by number\n- Use Conventional Commits for commit messages and PR titles, plus Gitea's `enhance` type for user-facing enhancements\n- Add an `Assisted-by: AGENT_NAME:MODEL_VERSION` trailer to commit messages, never `Co-Authored-By` or `Signed-off-by`\n- Attribute agent authorship on one trailing line in issue and PR comments, never as a PR description section\n- Never rewrite git history unless asked, update PRs with new commits and normal push\n- Comments: write almost none, short and preferably same-line, explaining why for a future reader. Never narrate code, the change or the prompt. Preserve existing ones that still apply. If you need to write a paragraph-long comment, rethink your implementation, it is likely too complicated\n- Add the current year to copyright headers of new `.go` files\n- In `options/locale`, only edit `locale_en-US.json`, other locales are synced automatically\n- In TS, use `!` instead of `?.`/`??` when a value always exists\n- In Go, prefer to use modern language features wherever possible\n- Prefer `tw-*` utilities over inline `style` and `flex-*` helpers over per-child `tw-ml-*`/`tw-mr-*` margins, falling back to `tw-*` where specificity requires `!important`\n- Run `make fmt` after `.go` edits, `make tidy` after `go.mod` edits, `make generate-swagger` after API changes, and lint what changed with `make lint-go`, `lint-js`, `lint-css` or `lint-templates`\n- Fix the cause rather than disabling a linter or weakening a test. Where unavoidable, use the narrowest scope with a trailing comment giving the reason\n- Run single tests with `go test -run '^TestName$' ./modulepath/` for Go, `pnpm exec vitest <path-filter>` for TS and `GITEA_TEST_E2E_FLAGS='<filepath>' make test-e2e` for e2e\n- Write the fewest, fastest tests covering the behavior, extending an existing one where possible. Prefer unit tests where logic is testable in isolation\n- Aim for sub-2s per integration test and sub-4s per e2e test. Wait on a deterministic condition rather than `sleep`, and prefer semantic locators in e2e tests\n"}}