One-click install
npx skills add https://github.com/kamp-us/phoenix --skill review-skill-kamp-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-skill
Source: https://github.com/kamp-us/phoenix/tree/main/claude-plugins/kampus-pipeline/skills/review-skill
Command: npx skills add https://github.com/kamp-us/phoenix --skill review-skill-kamp-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of skill PRs against their linked issue's acceptance criteria and a rigor checklist, ensuring behavioral correctness, trigger/description quality, cross-skill conflict/shadowing, and gate-invariant preservation before merging.

Core Features & Use Cases

  • Automated PR Verification: Automatically verify skill PRs against acceptance criteria and a rigor checklist.
  • Behavioral Correctness: Ensure the skill behaves as intended.
  • Trigger/Description Quality: Check the skill's trigger phrases and descriptions for accuracy.
  • Cross-Skill Conflict: Prevent conflicts between different skills.
  • Gate-Invariant Preservation: Ensure that the skill does not weaken any gates.
  • Use Case: Before merging a skill PR, use this Skill to automatically verify that it meets all the necessary criteria and does not introduce any conflicts or weaken any gates.

Quick Start

Run the review-skill command to verify the skill PR associated with the current issue.

Frequently Asked Questions about review-skill

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

FAQPage Schema
How do I automate skill PR verification against acceptance criteria?

To automate skill PR verification, run the review-skill command. It checks the pull request against linked issue acceptance criteria and a rigor checklist to ensure behavioral correctness before merging. Requires GitHub API access and a structured issue format.

What is gate-invariant preservation in skill PR verification?

Gate-invariant preservation ensures that a new skill PR does not weaken any existing gates. Automated verification checks the pull request against this requirement along with behavioral correctness and cross-skill conflict prevention to maintain system integrity.

How do I check for cross-skill conflicts before merging a skill PR?

To check for cross-skill conflicts before merging, run an automated verification against a rigor checklist. This process detects shadowing or conflicts between different skills, ensuring trigger and description quality alongside behavioral correctness.

Does skill PR verification require GitHub API access and structured issue formats?

Yes, skill PR verification requires GitHub API access and a structured issue format. The automation uses these dependencies to link pull requests with their corresponding acceptance criteria and rigor checklists for accurate behavioral and trigger quality validation.

What's the best way to validate trigger and description quality for software skills?

The best way to validate trigger and description quality is automated PR verification. It evaluates trigger phrases and descriptions for accuracy as part of a rigor checklist, preventing cross-skill conflicts and ensuring behavioral correctness before code integration.

When should I not use automated rigor checklist verification for skill PRs?

Automated rigor checklist verification is not suitable for unstructured issue formats or environments lacking GitHub API access. It specifically targets software development issue intake pipelines, so general code reviews without linked acceptance criteria fall outside its scope.