reviewer

Detect bugs, regressions, and concurrency issues in code submissions.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rk-terence/TokenPulse --skill reviewer-rk-terence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/rk-terence/TokenPulse/tree/main/.agents/skills/reviewer
Command: npx skills add https://github.com/rk-terence/TokenPulse --skill reviewer-rk-terence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reviewer Skill unit is designed to address the need for a focused code review process, helping teams identify and resolve bugs, regressions, and other critical issues before they impact production.

Core Features & Use Cases

  • Code Review Workflow: Facilitates a structured code review process, ensuring that changes are thoroughly inspected for quality and security.
  • Bug Detection: Identifies potential bugs, regressions, and concurrency issues early in the development cycle.
  • Use Case: For instance, when a developer submits a pull request, the reviewer Skill can be activated to automatically check for common issues and provide feedback.

Quick Start

Activate the reviewer Skill with the command: 'reviewer code changes in PR #123'.

Frequently Asked Questions about reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect bugs and regressions in a pull request?

Concurrency issues in code submissions are detected by analyzing code changes and their surrounding context during a structured code review process, ensuring that potential race conditions or thread conflicts are identified early.

What is the best way to automate code review for bug detection?

Automating code review for bug detection involves activating a review process upon code submission to inspect changes thoroughly for quality, security, and regressions, providing structured feedback to improve maintainability.

Can I use this to check code quality and concurrency issues without external dependencies?

Yes, you can check code quality and concurrency issues without external dependencies, as the review process operates independently to inspect submissions and provide meaningful feedback based on code changes and context.

How do I start a code review workflow for a new code submission?

To start a code review workflow for a new code submission, activate the reviewer Skill with a command targeting the specific changes, such as 'reviewer code changes in PR #123', to automatically check for common issues.

What are the limitations of automating regression testing during code review?

A limitation of automating regression testing during code review is that providing meaningful feedback requires sufficient analysis of code changes and context, meaning incomplete submissions may yield less accurate issue detection.