Address PR review comments. Use when the user says "check comments", "address comments", "fix PR feedback", or similar.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
devbydaniel, cursor[bot] (Bugbot)github-actions size warningsPR comments live in two separate API resources. Fetch both:
# 1. PR conversation comments (rare for review feedback, but check)
gh pr view <number> --json comments --jq \
'.comments[] | select(.author.login == "devbydaniel" or .author.login == "cursor[bot]") | "--- \(.author.login) at \(.createdAt) ---\n\(.body)\n"'
# 2. Inline review comments (where most feedback lives)
gh api repos/{owner}/{repo}/pulls/<number>/comments --jq \
'.[] | select(.user.login == "devbydaniel" or .user.login == "cursor[bot]") | "--- \(.user.login) at \(.created_at) on \(.path):\(.line // .original_line) ---\n\(.body)\n"'
The {owner}/{repo} can be read from gh repo view --json nameWithOwner --jq .nameWithOwner.
If no PR number is given, use the current branch:
gh pr view --json number --jq .number
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Query Ayunis deployed-environment telemetry in AppSignal — incidents, occurrence counts and error traces via the `appsignal-cli` binary; structured log attributes (user.id, org.id, nestjs.context, custom metadata) via the v2 logs API. Use when investigating a production/staging incident or log data — NOT for local dev logs (see backend-debugging).
The English summary is being prepared. Showing the original description.
Ayunis Core backend specifics — module boundaries, key files, and project conventions. Complements the nestjs-hexagonal-backend skill.
The English summary is being prepared. Showing the original description.
Frontend development in ayunis-core. Use when creating, modifying, or debugging frontend code (React, Feature-Sliced Design, API client).
The English summary is being prepared. Showing the original description.
Debug backend runtime errors (500s, crashes, unexpected behavior). Use when something is broken at runtime — not for writing new code.
The English summary is being prepared. Showing the original description.
Shared test fixtures for backend specs — port mock factories, domain builders, and shared IDs in a per-module testing/ folder. Use when a module's *.use-case.spec.ts files repeat the same mock-repository literal, inline entity construction, or hardcoded UUIDs across files.
The English summary is being prepared. Showing the original description.
Analyze Cursor Bugbot PR comments through a root-cause lens: is the finding valid, and is the suggested fix the real fix or a bandaid over a deeper problem? Use when the user asks to check, assess, or triage bugbot comments.
The English summary is being prepared. Showing the original description.