sr

Automate professional code reviews for ETNA_TRADER PRs and tasks.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tombelial666/test --skill sr-tombelial666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sr
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/sr
Command: npx skills add https://github.com/tombelial666/test --skill sr-tombelial666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct professional code reviews for ETNA_TRADER changes, ensuring consistency, policy alignment, and actionable findings across PRs and tasks.

Core Features & Use Cases

  • Token-efficient review workflow: enforces a lean, repeatable review process with clearly defined roles.
  • Gate-driven review protocol: applies standard LEAN or STRICT profiles depending on user request, and writes findings to a shared Code Review document.
  • Real-world use: review a PR for ETNA_TRADER to surface security, performance, and architectural concerns, then publish a concise summary for the orchestrator.

Quick Start

Initiate the SR review by loading the task path or PR URL and generate the Code Review file for ETNA_TRADER.

Frequently Asked Questions about sr

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

FAQPage Schema
How do I automate code reviews for ETNA_TRADER pull requests?

You can automate code reviews for ETNA_TRADER pull requests by loading the task path or PR URL to generate a standardized Code Review document. This coordinates parallel reviewer roles and consolidation to produce actionable PR readiness findings.

What is a gate-driven code review workflow?

A gate-driven code review workflow enforces a lean, repeatable review process using standard LEAN or STRICT profiles. It coordinates parallel reviewer roles through structured gates, writing consolidated findings to a shared Code Review markdown document.

Can I use this automated review process for task documents as well as PRs?

Yes, the automated review process applies to both pull requests and task documents for ETNA_TRADER changes. It enforces a structured workflow with frontmatter-driven metadata and section markers to ensure consistency and policy alignment across both formats.

What's the best way to structure code review findings for pull request readiness?

The best way to structure code review findings is using a standardized output artifact with frontmatter-driven metadata and section markers. This enforces a structured workflow that surfaces security, performance, and architectural concerns in a concise summary.

Does the review workflow support different strictness levels for security and architecture checks?

Yes, the review workflow supports different strictness levels by applying standard LEAN or STRICT gate profiles depending on your request. This ensures policy alignment and actionable findings for security, performance, and architectural concerns.

How do I consolidate parallel code review roles into a single document?

You can consolidate parallel code review roles into a single document through the gate-driven consolidation process. This coordinates multiple reviewer roles and writes their unified findings into a standardized Code Review markdown artifact for orchestrator publication.