Praca z narzędziem

Review a change

Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".

fe-reviewkażdego projektu webowego5 regułładowane zawsze: 80 tokenów; przy użyciu: 787 tokenów; w referencjach na żądanie: 789 tokenów.

Instalacja

init instaluje ten skill, gdy projekt używa: każdego projektu webowego. Wybierz agenta, aby zobaczyć, gdzie trafią jego pliki.

npx github:dawidolko/frontend-skills init

Ten sposób nie był jeszcze testowany. npx i pnpm dlx są przetestowane; jeśli ten zawiedzie, użyj jednego z nich.

Bez --agents polecenie init rozpoznaje agentów po tym, co projekt już ma, a gdy nie znajdzie żadnego, pyta:

Po czym init rozpoznaje każdego z agentów (17)

Agent	Rozpoznawany po
Claude Code	`CLAUDE.md` `.claude` `CLAUDE.local.md`
OpenAI Codex	`.codex` `AGENTS.override.md`
Cursor	`.cursor` `.cursorrules`
GitHub Copilot	`.github/copilot-instructions.md` `.github/instructions` `.github/skills` `.github/prompts`
Gemini CLI	`GEMINI.md` `.gemini`
Antigravity CLI	`.agents/rules` `.agent/rules`
Devin / Windsurf	`.devin` `.windsurf` `.windsurfrules`
OpenCode	`opencode.json` `opencode.jsonc` `.opencode`
Cline	`.clinerules` `.cline`
Zed	`.rules` `.zed`
JetBrains Junie	`.junie`
Kiro	`.kiro`
Augment	`.augment` `.augment-guidelines`
Trae	`.trae`
Continue	`.continue`
Amazon Q Developer	`.amazonq`
Aider	`.aider.conf.yml` `CONVENTIONS.md`

Gdzie trafia fe-review dla: Claude Code

.claude/skills/fe-review/SKILL.mdskill
.claude/skills/fe-review/references/review.mdskill
.claude/rules/fe-review.mdplik reguł
CLAUDE.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.claude/rules/fe-review.md

---
paths:
  - "**/*.html"
  - "**/*.jsx"
  - "**/*.tsx"
  - "**/*.js"
  - "**/*.vue"
  - "**/*.svelte"
  - "**/*.astro"
  - "**/*.css"
  - "**/*.scss"
---

# Review a change (frontend-skills)

Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.claude/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: OpenAI Codex

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

OpenAI Codex nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: Cursor

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
.cursor/rules/fe-review.mdcplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.cursor/rules/fe-review.mdc

---
description: Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".
globs: **/*.html, **/*.jsx, **/*.tsx, **/*.js, **/*.vue, **/*.svelte, **/*.astro, **/*.css, **/*.scss
alwaysApply: false
---

# Review a change (frontend-skills)

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.agents/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: GitHub Copilot

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
.github/instructions/fe-review.instructions.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.github/instructions/fe-review.instructions.md

---
applyTo: "**/*.html,**/*.jsx,**/*.tsx,**/*.js,**/*.vue,**/*.svelte,**/*.astro,**/*.css,**/*.scss"
description: "Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or \"check my changes before I push\"."
---

# Review a change (frontend-skills)

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.agents/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Gemini CLI

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
GEMINI.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Gemini CLI: Gemini CLI was replaced by Antigravity CLI for unpaid tiers on 2026-06-18; choose "antigravity" too if you use it.

Gemini CLI nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

GEMINI.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: Antigravity CLI

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
.agents/rules/fe-review.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.agents/rules/fe-review.md

---
trigger: glob
globs: "**/*.html, **/*.jsx, **/*.tsx, **/*.js, **/*.vue, **/*.svelte, **/*.astro, **/*.css, **/*.scss"
description: "Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or \"check my changes before I push\"."
---

# Review a change (frontend-skills)

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.agents/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Devin / Windsurf

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
.devin/rules/fe-review.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Devin / Windsurf: Devin CLI also reads .cursor/rules; with Cursor chosen too, the CLI sees both rule files of a skill.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.devin/rules/fe-review.md

---
trigger: glob
globs: "**/*.html,**/*.jsx,**/*.tsx,**/*.js,**/*.vue,**/*.svelte,**/*.astro,**/*.css,**/*.scss"
---

# Review a change (frontend-skills)

Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.agents/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: OpenCode

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

OpenCode nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: Cline

.claude/skills/fe-review/SKILL.mdskill
.claude/skills/fe-review/references/review.mdskill
.clinerules/fe-review.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Cline: If .clinerules is a single file rather than a folder, Cline rule files are not written; skills still are.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.clinerules/fe-review.md

---
paths:
  - "**/*.html"
  - "**/*.jsx"
  - "**/*.tsx"
  - "**/*.js"
  - "**/*.vue"
  - "**/*.svelte"
  - "**/*.astro"
  - "**/*.css"
  - "**/*.scss"
---

# Review a change (frontend-skills)

Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.claude/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Zed

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
CLAUDE.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zed: Zed reads only the first instruction file of its list; the block is placed in that file.

Zed nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

CLAUDE.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: JetBrains Junie

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

JetBrains Junie: Junie reads .agents/skills only in a trusted project.

JetBrains Junie nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: Kiro

.kiro/skills/fe-review/SKILL.mdskill
.kiro/skills/fe-review/references/review.mdskill
.kiro/steering/fe-review.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.kiro/steering/fe-review.md

---
inclusion: fileMatch
fileMatchPattern: ["**/*.html", "**/*.jsx", "**/*.tsx", "**/*.js", "**/*.vue", "**/*.svelte", "**/*.astro", "**/*.css", "**/*.scss"]
---

# Review a change (frontend-skills)

Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or "check my changes before I push".

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.kiro/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Augment

.agents/skills/fe-review/SKILL.mdskill
.agents/skills/fe-review/references/review.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Augment nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-review dla: Trae

.trae/skills/fe-review/SKILL.mdskill
.trae/skills/fe-review/references/review.mdskill
.trae/rules/fe-review.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Trae: Trae reads AGENTS.md only after it is enabled in its settings.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.trae/rules/fe-review.md

---
description: "Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or \"check my changes before I push\"."
globs: **/*.html,**/*.jsx,**/*.tsx,**/*.js,**/*.vue,**/*.svelte,**/*.astro,**/*.css,**/*.scss
alwaysApply: false
---

# Review a change (frontend-skills)

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.trae/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Continue

.frontend-skills/skills/fe-review/SKILL.mdskill
.frontend-skills/skills/fe-review/references/review.mdskill
.continue/rules/fe-review.mdplik reguł

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.continue/rules/fe-review.md

---
name: "Review a change"
description: "Reviews a diff or pull request of front-end code - runs audit --changed, maps the touched files to their skills, walks the manual rules of those skills (keyboard, screen reader, motion, content), and reports findings by rule id with file, line and fix. Use when asked to review a pull request, a branch, staged changes or a component, or \"check my changes before I push\"."
globs: ["**/*.html", "**/*.jsx", "**/*.tsx", "**/*.js", "**/*.vue", "**/*.svelte", "**/*.astro", "**/*.css", "**/*.scss"]
alwaysApply: false
---

# Review a change (frontend-skills)

- Start with the tool: `npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json`.
- Review only what the change touches; mention older problems once, separately, without blocking on them.
- Map each touched file to its skills (by file type and framework) and walk their manual rules too.
- Report every finding as rule id, `file:line`, one sentence why, and the fix; link `explain <id>` instead of pasting rule text.
- New `fs-ignore` comments need a rule id and a reason (tooling/ignore-with-reason).
- Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
- Test changes: no `.only`, no fixed waits, assertions that users would notice (test/no-focused-tests).
- Separate blocking findings (at or above `failOn`) from suggestions; never block on taste.
- Never approve on the audit alone; say what was checked automatically and what still needs a person.

Before larger changes, read the full skill: `.frontend-skills/skills/fe-review/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-review dla: Amazon Q Developer

.frontend-skills/skills/fe-review/SKILL.mdskill
.frontend-skills/skills/fe-review/references/review.mdskill
.amazonq/rules/frontend-skills.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Amazon Q Developer: Amazon Q Developer IDE plugins reach end of support on 2027-04-30; AWS points to Kiro.

Amazon Q Developer nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.amazonq/rules/frontend-skills.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

### Skills

- `fe-review` (Review a change): when editing `**/*.html`, `**/*.jsx`, `**/*.tsx`, `**/*.js`, `**/*.vue`, `**/*.svelte`, `**/*.astro`, `**/*.css`, `**/*.scss`, first read `.frontend-skills/skills/fe-review/SKILL.md`.

Prawdziwy plik

Gdzie trafia fe-review dla: Aider

.frontend-skills/skills/fe-review/SKILL.mdskill
.frontend-skills/skills/fe-review/references/review.mdskill
CONVENTIONS.mdblok instrukcji
.aider.conf.ymlkonfiguracja

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Aider nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

CONVENTIONS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

### Skills

- `fe-review` (Review a change): when editing `**/*.html`, `**/*.jsx`, `**/*.tsx`, `**/*.js`, `**/*.vue`, `**/*.svelte`, `**/*.astro`, `**/*.css`, `**/*.scss`, first read `.frontend-skills/skills/fe-review/SKILL.md`.

Prawdziwy plik

Jak go używać

Po instalacji agent sam ładuje skill, gdy zadanie pasuje do jego opisu. Możesz też poprosić o niego własnymi słowami, na przykład:

Frazy z opisu skilla, po których agent go wybiera (po angielsku, jak w skillu):

check my changes before I push

A żeby sprawdzić i poprawić pracę:

Użyj skilla fe-review na tym pliku.
Uruchom audyt front-endu na moich zmianach i popraw wszystko, co poważne.
Wyjaśnij tooling/ignore-with-reason i popraw to tutaj.

Reguły, których uczy

tooling/ignore-with-reason
Every fs-ignore comment names the rule id it silences and says why; a bare fs-ignore silences every rule on the line.
umiarkowanaręczne
a11y/no-keyboard-trap
Keyboard focus can always leave a component with Tab, Shift+Tab or Escape; only an open modal keeps focus inside.
krytycznaręczneWCAG 2.1.2
a11y/status-message-live
Messages that appear without moving focus (saved, results, errors, progress) are announced through a live region.
poważnaręczneWCAG 4.1.3
a11y/focus-not-obscured
Sticky headers, footers, cookie banners and chat widgets never fully cover the element that has keyboard focus.
poważnaręczneWCAG 2.4.11
test/no-focused-tests
No focused tests (.only, fit, fdescribe) are committed; they silently skip the rest of the suite.
poważnastatyczne

Skrót reguł

Ta część jest kopiowana do zawężonego pliku reguł każdego agenta, więc musi być zrozumiała sama w sobie:

Start with the tool: npx github:dawidolko/frontend-skills audit --changed --base <target branch> --json.
Review only what the change touches; mention older problems once, separately, without blocking on them.
Map each touched file to its skills (by file type and framework) and walk their manual rules too.
Report every finding as rule id, file:line, one sentence why, and the fix; link explain <id> instead of pasting rule text.
New fs-ignore comments need a rule id and a reason (tooling/ignore-with-reason).
Interactive changes get a keyboard and screen reader check: no traps, announced status messages, focus not hidden (a11y/no-keyboard-trap, a11y/status-message-live, a11y/focus-not-obscured).
Test changes: no .only, no fixed waits, assertions that users would notice (test/no-focused-tests).
Separate blocking findings (at or above failOn) from suggestions; never block on taste.
Never approve on the audit alone; say what was checked automatically and what still needs a person.

Kroki, które wykonuje agent

Get the diff: git diff --name-only <base>...HEAD (or the pull request's files). Note the frameworks from the profile.
Run audit --changed --base <base> --json; every finding on a changed line is in scope.
For each touched area, open its skill's ## Rules and check the manual ones against the diff: forms (fe-a11y-forms), widgets (fe-a11y-dialog, -menus, -tabs-accordion, -combobox), media, i18n, security sinks, performance of new dependencies and images.
If a preview URL exists and the person agrees, run audit --url <preview> for contrast, rendered names and Lighthouse.
Write the review: blocking findings, suggestions, manual checks done, manual checks left for a person.

Jak agent sprawdza swoją pracę

Every finding has a real rule id (list --rules) or is clearly marked as a suggestion without one.
The review says which commands ran and their result.

Sprawdzane audytem

Testy statyczne tych reguł działają w audit; to prawdziwa sesja na przykładowym projekcie:

Nagranie terminala: audit wypisuje znaleziska według wagi z identyfikatorami reguł i miejscem plik:linia i kończy się błędem od progu serious. — `audit`: liczby według wagi, każda reguła z pierwszym miejscem, kod wyjścia.

Pliki referencyjne

references/review.md789 tokenów

SKILL.md na GitHubie