skills.rest
shinpr
shinprCOMMUNITY
Explore all skills by this author →
Website𝕏@shinpr_pGitHub

recipe-quality-profile

Creates repository-specific quality acceptance profiles in docs/project-context/quality.yaml after user confirmation.

675|103|Updated Oct 10, 2025
Search Tags:#acceptance criteria#YAML#Validation#repository policy#quality profile#Code review
One-click install
npx skills add https://github.com/shinpr/claude-code-workflows --skill recipe-quality-profile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recipe-quality-profile
Source: https://github.com/shinpr/claude-code-workflows/tree/main/dev-workflows/skills/recipe-quality-profile
Command: npx skills add https://github.com/shinpr/claude-code-workflows --skill recipe-quality-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack explicit, repository-owned acceptance criteria for implementation and code review, so quality decisions drift between contributors and AI agents. This Skill turns evidence found in the repository into a confirmed, versioned quality profile.

Core Features & Use Cases

  • Evidence-based profile authoring: Derives candidate quality dimensions from repository instructions, CI, manifests, schemas, tests, and implementation patterns, citing supporting and contradicting evidence.
  • Confirmation-gated writes: Presents proposed additions, changes, and removals with unresolved policy choices, and writes to docs/project-context/quality.yaml only after explicit user confirmation.
  • Contract validation: Verifies version 1, unique dimension IDs, observable pass conditions, applies_when scoping, and readable evidence references after writing.
  • Use Case: A maintainer asks to codify that all public API changes must update the OpenAPI schema; the Skill inspects the repo for supporting evidence, proposes a dimension, and writes the confirmed profile.

Quick Start

Ask the assistant to create or update the repository quality profile for a specific policy change, then review and confirm the proposed dimensions before they are written.

Frequently Asked Questions about recipe-quality-profile

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

FAQPage Schema
How do I create a quality profile for my repository?▼

Invoke the skill with the policy change you want captured. It inspects repository instructions, CI, manifests, schemas, tests, and code patterns, proposes evidence-backed dimensions, and writes docs/project-context/quality.yaml only after you confirm the proposal.

What is the format of the quality.yaml profile?▼

The profile uses version 1 with a review_dimensions list. Each dimension has a stable kebab-case id, an applies_when condition limiting its scope, a positive observable pass condition, and evidence entries citing repository paths, sections, or contracts.

Does the skill modify the repository without confirmation?▼

No. It presents proposed additions, changes, removals, supporting and contradicting evidence, and unresolved policy choices first. The profile is written only after explicit user confirmation of a proposal with no unresolved choices.

What happens when no repository evidence supports a quality dimension?▼

Candidates lacking required repository evidence are omitted, and the exact missing evidence is reported. If no repository-specific dimension remains and no profile exists, the repository is left unchanged.

How are updates to an existing quality profile handled?▼

The requested policy change defines the update boundary. Candidates are derived only from that change, unrelated dimensions are preserved, and the written result is validated for unique IDs, required fields, and consistency with the confirmed proposal.

Related Skills

Explore More Software Engineering Skills→
kapilvirenahujakapilvirenahuja
3

infer-project-profile-from-code

Infer a project-profile artifact from scan-index.json evidence.

Community
Advanced
CaptainCrouton89CaptainCrouton89
497

Reviewing Code

Evaluate code changes for security, correctness, performance, and spec alignment.

Community
Basic
bennybennisonbennybennison

document-ownership

Establish document ownership hierarchies and prevent duplication across governance documents.

Community
Intermediate
tomasbassotomasbasso

code-review-excellence

Provides structured, constructive code review feedback and checklists for pull requests.

Community
Advanced