skills.rest
learn-ukrainian
learn-ukrainianOFFICIAL
Explore all skills by this author →
GitHub

prompt-review

Analyze orchestration folders to identify prompt engineering issues and generate bug reports.

9|4|Updated Dec 21, 2025
Search Tags:#debugging#orchestration#gemini#prompt-engineering#friction#prompt-review
One-click install
npx skills add https://github.com/learn-ukrainian/learn-ukrainian.github.io --skill prompt-review-learn-ukrainian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-review
Source: https://github.com/learn-ukrainian/learn-ukrainian.github.io/tree/main/claude_extensions/skills/prompt-review
Command: npx skills add https://github.com/learn-ukrainian/learn-ukrainian.github.io --skill prompt-review-learn-ukrainian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze orchestration folders to identify prompt/context engineering problems. Every friction report is a prompt engineering bug report.

Core Features & Use Cases

  • Identify root causes of prompt failures across orchestration modules
  • Produce actionable fixes and cross-module insights for prompt templates
  • Use case: QA teams auditing modules to reduce recurring friction and improve reliability

Quick Start

Provide the track slug and module slug (e.g., a1 the-cyrillic-code-i) to begin the review.

Frequently Asked Questions about prompt-review

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

FAQPage Schema
How do I audit orchestration prompts for prompt engineering bugs?▼

The Skill analyzes orchestration folders to identify prompt and context engineering issues, converting friction reports into structured bug reports. It surfaces root causes of prompt failures and provides actionable fixes for prompt templates and Gemini prompts.

What do I need to provide to start a prompt review?▼

You must provide the track slug and module slug to begin the review. Access to orchestration folders and phase documents, such as phase-2-prompt.md and phase-2-friction.md, is required to produce accurate bug reports.

Why do my Gemini prompts keep failing across orchestration modules?▼

Gemini prompts fail due to underlying prompt and context engineering issues within orchestration modules. Auditing these folders surfaces root causes and cross-module friction points, enabling actionable fixes and batch-grade summaries to improve reliability.

Can I generate batch-grade summaries for curriculum modules?▼

Yes, you can generate batch-grade summaries for curriculum modules. The review process analyzes modules within curriculum tracks to surface prompt bugs, enabling QA teams to reduce recurring friction and improve reliability.

What is the best way to turn friction reports into actionable prompt fixes?▼

The best way is to treat every friction report as a prompt engineering bug report. Analyzing phase documents and orchestration folders converts these findings into structured bug reports with root causes and actionable fixes.

Related Skills

Explore More Software Engineering Skills→
filipexyzfilipexyz
1

claude-code-cli

Develop autonomous agents and orchestrate multi-agent systems with Claude Code CLI.

Community
Advanced
zangjeicyzangjeicy

adversarial-ux-test

Simulate an adversarial user persona to test web application UX friction.

Community
Advanced
learn-ukrainianlearn-ukrainian
9

batch-review

Orchestrate batch prompt and content reviews across curriculum modules into audit reports.

Official
Advanced
joesysjoesys
1

gemini

Forward prompts to the Gemini CLI and display its full response verbatim.

Community
Advanced