skills.rest
ITSalt
ITSaltCOMMUNITY
Explore all skills by this author →
GitHub

nacl-tl-review

Review completed tasks against BE, FE, or TECH checklists and produce a review artifact.

23|2|Updated Apr 10, 2026
Search Tags:#tdd#quality-assurance#code-review#artifact#software-engineering
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nacl-tl-review
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-review
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review for completed tasks (BE, FE, or TECH). Use when: review code, code review, check implementation, verify task, approve development, or the user says "/nacl-tl-review UC### --be" or "/nacl-tl-review UC### --fe". Flags: --be for backend review, --fe for frontend review, no flag for TECH tasks.

Core Features & Use Cases

  • Identify review mode from the command and select the appropriate checklist (BE, FE, or TECH).
  • Run the stub verification gate before proceeding with quality checks.
  • Read task files from .tl/tasks/UC###/ and read development results to verify acceptance criteria and TDD compliance.
  • Apply the relevant review checklist, produce a review artifact, and update tracking status.
  • Ensure a constructive, actionable feedback loop and clear next steps.

Quick Start

Start a review by invoking /nacl-tl-review UC### with --be for backend reviews, --fe for frontend, or no flag for TECH, then proceed with the stub gate and artifact creation.

Frequently Asked Questions about nacl-tl-review

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

FAQPage Schema
How do I automate code review for backend and frontend tasks?▼

Automate code review by invoking the review command with --be for backend or --fe for frontend, which selects the appropriate checklist to verify acceptance criteria, TDD compliance, and code quality.

What is the best way to verify TDD compliance during a code review?▼

Verify TDD compliance by reading task files and development results from the task directory, applying the relevant review checklist to ensure tests meet acceptance criteria before producing a review artifact.

How does a stub verification gate work in task code reviews?▼

The stub verification gate executes before quality checks during a code review, ensuring foundational requirements are met before proceeding to evaluate backend, frontend, or technical task artifacts.

Can I review technical tasks that are not strictly backend or frontend?▼

Review technical tasks by running the command with no flag, which selects the TECH checklist to evaluate implementation quality and generate the appropriate review artifact for technical work.

How do I document blockers and next steps after reviewing completed code?▼

Document blockers and next steps by producing a review artifact that updates the tracking status, records the final decision, and provides the team with actionable feedback for resolution.

Related Skills

Explore More Software Engineering Skills→
ITSaltITSalt
23

nacl-tl-qa

Automate end-to-end QA testing of UC tasks with MCP Playwright.

Community
Advanced
CurryTangCurryTang
174

project-todo-manager

Manage ResearchOps project TODOs with status updates and next-step recommendations.

Community
Advanced
CENKSSSCENKSSS

qe-iterative-loop

Automate iterative quality assurance loops for test execution and coverage analysis.

Community
Advanced
Veloxia-agencyVeloxia-agency

ship-gate

Audit codebases for pre-production shipping risks across eight release-readiness categories.

Community
Advanced