Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/).
Install Fix Frontend Review Comments
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .claude/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .claude/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-commentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .agents/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .agents/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .cursor/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .cursor/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JetBrains/kotlin-web-site.git --path .claude/skills/fix-frontend-review-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .gemini/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .gemini/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-commentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .github/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .github/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/kotlin-web-site fix-frontend-review-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/kotlin-web-site.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/fix-frontend-review-comments .opencode/skills/fix-frontend-review-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fix-frontend-review-comments" agent skill from https://github.com/JetBrains/kotlin-web-site/tree/master/.claude/skills/fix-frontend-review-comments into .opencode/skills/fix-frontend-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-frontend-review-comments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fix-frontend-review-comments- GitHub stars
- 1.6k
- Token cost
- ~444 tokens
- SKILL.md length
- 147 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/).
- Apply reviewer comments on a PR
- Calls gh
- An automation feeds in review threads to resolve
What it does
Fix Frontend Review Comments is an agent skill from JetBrains/kotlin-web-site, published by the product's own GitHub organization. Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/). Use when asked to fix, address, or apply reviewer comments on a PR, or when an automation feeds in review threads to resolve. Covers fetching unresolved threads with gh, the in-scope/out-of-scope path fence, the project conventions from .ai/guidelines.md, the lint / tsc / Playwright gates, committing, and the machine-readable report the…
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Android development, Pull requests and Browser testing. It works with Kotlin, Playwright, Next.js and React. The repository describes itself as: The Kotlin programming language website. The licence is Apache-2.0.
When your agent uses it
- Apply reviewer comments on a PR
- An automation feeds in review threads to resolve
Example prompts
- “/fix-frontend-review-comments”
What it can do on your machine
Read from SKILL.md and the folder at commit 38512ff. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fix Frontend Review Comments loads about 444 tokens when it runs. Until then it costs about 151 tokens; SKILL.md has 147 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JetBrains/kotlin-web-site at commit 38512ff, republished under its Apache-2.0 licence (© JetBrains). 147 words, ~444 tokens.
Download SKILL.mdSave it as
.claude/skills/fix-frontend-review-comments/SKILL.md (or your agent's skills folder).- name
- fix-frontend-review-comments
- description
- Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/). Use when asked to fix, address, or apply reviewer comments on a PR, or when an automation feeds in review threads to resolve. Covers fetching unresolved threads with gh, the in-scope/out-of-scope path fence, the project conventions from .ai/guidelines.md, the lint / tsc / Playwright gates, committing, and the machine-readable report the automation parses. Not for docs/, data/, or .teamcity/ comments.
Fix frontend review comments
The full instructions live in .ai/prompts/fix-frontend-review-comments.md.
That file is the source of truth and is also injected verbatim by CI automation, so this skill and
the automated runs behave identically.
Read that file now and follow it exactly. Do not paraphrase it from memory.
Inputs it expects (pass whatever the user gave you; the rest have safe defaults):
PR_NUMBERorPR_URL— required.REVIEW_COMMENTS— pre-supplied threads; if absent, the prompt fetches unresolved threads viagh api graphql.COMMENT_IDS— restrict the run to specific threads.ALLOW_PUSH,ALLOW_REPLY— defaultfalse. When a human invokes this skill interactively, leave them off unless they explicitly ask you to push or to reply on GitHub.
Two things worth restating because they are the usual failure modes:
.ai/guidelines.mdis binding for every edit.- Out-of-scope paths (
docs/,data/**,redirects/,.teamcity/,.github/,scripts/, dependency versions) are escalated in the report, never edited.
© JetBrains, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/fix-frontend-review-comments of JetBrains/kotlin-web-site.
Open the folder on GitHubat commit 38512ff
Compare with similar skills
Fix Frontend Review Comments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fix Frontend Review Comments this skillJetBrains/kotlin-web-site | 1.6k | — | ~444 | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Liteyuki Webui FrontendLiteyukiStudio/LiteyukiBot | 157 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Playwright Coretestdino-hq/playwright-skill | 390 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Test Revieweraxelixlabs/axelix | 148 | — | ~3.2k | Automated safety check: Pass | LGPL-3.0 | |
| Code Reviewerjewbetcha/opentrace | 116 | 2 repos | ~1.1k | Automated safety check: Notes | MIT |
Similar skills
Liteyuki Webui Frontend
LiteyukiStudio/LiteyukiBot
Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/.
Playwright Core
testdino-hq/playwright-skill
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests.
Test Reviewer
axelixlabs/axelix
Reviews test code in GitHub pull requests for isolation, public-API contract coverage, AAA structure, and correct exception assertions.
Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
Build Nitro Modules
margelo/react-native-skills
Builds and designs React Native Nitro Modules with Nitrogen, HybridObject TypeScript specs, Nitro View components, generated native implementations, zero-copy and native-state APIs, Swift/Kotlin/C++…
More from JetBrains/kotlin-web-site
- Official
Add Writerside Doc Module
JetBrains/kotlin-web-site
Add a new external Writerside documentation source to kotlin-web-site via the TeamCity Kotlin DSL (as a sub-documentation source under KotlinWithCoroutines).
- Official
Add API Reference
JetBrains/kotlin-web-site
Publish a new kotlinx library API reference on kotlinlang.org/api via the TeamCity Kotlin DSL, the way kotlinx.coroutines, kotlinx.serialization, kotlinx-datetime and kotlinx-io are published.
Related
Works with
Categories
Questions about Fix Frontend Review Comments
What does Fix Frontend Review Comments do?
Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/). Fix Frontend Review Comments is an agent skill from JetBrains/kotlin-web-site, published by the product's own GitHub organization.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/).
When should I use Fix Frontend Review Comments?
Fix Frontend Review Comments fits situations like: apply reviewer comments on a PR; an automation feeds in review threads to resolve.
How do I install Fix Frontend Review Comments in Claude Code?
Run `npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a claude-code`. Or copy the skill folder (.claude/skills/fix-frontend-review-comments in JetBrains/kotlin-web-site) into .claude/skills/fix-frontend-review-comments in your project. Claude Code loads it when a task matches its description.
How do I install Fix Frontend Review Comments in Codex?
Run `npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a codex`. Or copy the skill folder (.claude/skills/fix-frontend-review-comments in JetBrains/kotlin-web-site) into .agents/skills/fix-frontend-review-comments in your project. Codex loads it when a task matches its description.
Can I use Fix Frontend Review Comments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetBrains/kotlin-web-site --skill fix-frontend-review-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-frontend-review-comments, .gemini/skills/fix-frontend-review-comments, .github/skills/fix-frontend-review-comments and .opencode/skills/fix-frontend-review-comments in your project.
What does Fix Frontend Review Comments need to run?
Going by SKILL.md and its folder, Fix Frontend Review Comments needs the command-line tools its instructions call (gh).
Does Fix Frontend Review Comments access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Fix Frontend Review Comments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fix Frontend Review Comments use?
Fix Frontend Review Comments is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fix Frontend Review Comments use?
About 444 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fix Frontend Review Comments?
Skills that share tags, products or a category with Fix Frontend Review Comments: Code Review (nteract/semiotic, 2.7k stars), Liteyuki Webui Frontend (LiteyukiStudio/LiteyukiBot, 157 stars), Playwright Core (testdino-hq/playwright-skill, 390 stars) and Test Reviewer (axelixlabs/axelix, 148 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fix Frontend Review Comments?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/kotlin-web-site, which has 1,625 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.
Source: JetBrains/kotlin-web-site on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.