Skip to content

A modern and easy to use dashboard. 80+ integrations. 20K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration.

docs(agents): require browser before/after evidence for AI PRs and restrict triage skill to maintainers (#7283)

Thomas1d389208e67b
diff --git a/.agents/skills/homarr-triage/SKILL.md b/.agents/skills/homarr-triage/SKILL.md
index 8cfbe47b2..b51cbe9a9 100644
--- a/.agents/skills/homarr-triage/SKILL.md
+++ b/.agents/skills/homarr-triage/SKILL.md
@@ -1,10 +1,13 @@
---
name: homarr-triage
-description: Triage Homarr GitHub issues and pull requests, refresh reporter follow-ups, prioritize investigations, and operate the triage Project. Use for queue updates and approved issue work, including contributor PRs.
+description: Maintainer-only. Triage Homarr GitHub issues and pull requests, refresh reporter follow-ups, prioritize investigations, and operate the triage Project. Use only when a Homarr maintainer explicitly invokes it; never for fixing an issue or opening a contribution PR.
+disable-model-invocation: true
---
# Homarr Triage
+This skill is for Homarr maintainers operating the triage queue. If you are fixing an issue or opening a PR as a contributor, stop: follow "AI-assisted pull requests" in `AGENTS.md` and do not use this skill's disclaimer.
+
Work in `homarr-labs/homarr`. Treat an issue and its implementation PR as one investigation, while retaining their separate testing and review states.
## Load the contract
diff --git a/.agents/skills/homarr-triage/agents/openai.yaml b/.agents/skills/homarr-triage/agents/openai.yaml
index 36dc6d500..4bd83273e 100644
--- a/.agents/skills/homarr-triage/agents/openai.yaml
+++ b/.agents/skills/homarr-triage/agents/openai.yaml
@@ -1,3 +1,6 @@
interface:
display_name: "Homarr Triage"
- short_description: "Triage Homarr issues, PRs, and Project follow-ups"
+ short_description: "Maintainer-only: triage Homarr issues, PRs, and Project follow-ups"
+
+policy:
+ allow_implicit_invocation: false
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index dbaab3791..2b60bb401 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -12,6 +12,8 @@
- [ ] No shorthand variable names are used (for example, `x`, `y`, `i`, or abbreviations)
- [ ] Documentation under `apps/docs` is updated only when users need new or corrected information to use the app
- [ ] When using AI, no temporary files are checked in and the code style follows the rest of the project
+- [ ] When using AI, the PR follows "AI-assisted pull requests" in `AGENTS.md`, including a before/after screenshot table
+ for user-visible changes
**When contributing a new integration or widget:**
diff --git a/AGENTS.md b/AGENTS.md
index 765db4224..17dc185e7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -99,6 +99,17 @@ Only after this user-need test passes, use these locations:
Add tests only when requested, and only when the test is extremely relevant and will plausibly prevent a future regression in user-visible behavior or a security boundary. Do not add tests that restate implementation details or duplicate stronger coverage. For focused changes, run only the relevant existing or newly requested checks when validation is needed. Do not run broad test, Docker, or E2E suites by default.
+## AI-assisted pull requests
+
+These rules apply to every PR an agent prepares or opens, including contributor PRs. A PR that does not meet them will be closed.
+
+- Prove the change in the running app. Start Homarr locally, reproduce the reported case on unmodified `dev`, then repeat it on the PR head using `agent-browser` (`agent-browser skills get core` loads its workflow). Use the same viewport, theme, fixture data and settings for both captures.
+- The PR body must open with a before/after table of those screenshots, uploaded with `gh pr create --attach` (or `gh pr comment --attach`). Local paths, mock-ups and test-runner output are not substitutes. Read back the published body and check the images render.
+- For behavior that only shows over time (polling, refresh, notifications), capture the same view at the relevant moments, or a short recording, in the same table.
+- Changes with no user-visible effect (types, internal refactors, CI) state that in one line instead of the table.
+- Keep the body short: the problem, the resulting behavior, the evidence table, and one or two lines of relevant validation. No validation logs, environment recitals, private replay descriptions or checklists of what was not tested.
+- Do not use the `homarr-triage` skill or its `> _This was generated by AI during triage._` disclaimer; that workflow is for maintainers only. Disclose AI assistance in plain words instead.
+
## MCP servers
`.mcp.json` declares project-scoped MCP servers. Keep only keyless definitions there; credentials belong in local dotfiles. See [Mantine LLM tooling](https://mantine.dev/guides/llms/) for client-specific setup.
@@ -111,7 +122,7 @@ Portable skills live in `.agents/skills/`. Read the relevant `SKILL.md` before w
- `documentation-sync` — user-critical documentation only
- `mcp-integration` — safe tRPC-to-MCP exposure
- `homarr-custom-widget` — safe Custom JSX v2 authoring
-- `homarr-triage` — issue/PR queues, reporter follow-ups, and GitHub Project operations
+- `homarr-triage` — maintainer-only, explicit invocation; issue/PR queues, reporter follow-ups, and GitHub Project operations
### Issue tracker