Loading...
Loading...
Found 113 Skills
Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.
Structured review process for Remotion video implementations. Analyzes spec compliance, detects common timing/easing issues, validates asset quality, and provides prioritized revision lists. Use when reviewing Remotion code against design specs or performing quality assurance on video compositions. Trigger phrases "review video code", "check spec compliance", "audit Remotion implementation".
Validates planning artifacts (spec.md, plan.md, data-model.md, contracts/) for quality, completeness, and consistency. Checks for mandatory sections, cross-artifact consistency, and constitution compliance. Always run after /speckit.plan completes.
Use when the user asks to create a pull request, open a PR, submit changes for review, or says "/pr". Validates branch state, analyzes all commits since divergence from base, runs pre-PR quality checks, generates structured PR title and body with summary/test-plan/breaking-changes sections, pushes branch, and creates the PR via GitHub CLI (gh). Supports draft PRs, reviewer assignment, and label attachment.
작업 완료 전 품질 증거를 수집하는 게이트. test, lint, build 결과와 잔여 리스크(TODO, any 타입, console.log)를 검증하여 통과/실패 판정한다. 팀 스킬 완료 시 자동 호출되거나 수동으로 실행 가능.
Perform non-destructive cross-artifact consistency and quality analysis on three core documents: spec.md, plan.md, and tasks.md. Identify inconsistent, duplicate, ambiguous, and under-specified items after task generation. Trigger words include: "speckit-analyze", "speckit-analyze", "document consistency analysis", "specification analysis", "quality check", "artifact analysis", "spec analysis", "plan analysis", "task analysis"
Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership.
Audit project documentation quality across 8 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy, Stack Adaptation, Semantic Content). Delegates to ln-601 for deep semantic verification of project documents. Use when documentation needs quality review, after major doc updates, or as part of ln-100-documents-pipeline. Outputs Compliance Score X/10 per category + Findings + Recommended Actions.
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
Per-package implementation review producing structured findings per review-findings.schema.json
Use when running project-wide lint across a Datex Studio codebase (or a scope subset) — checks 5 categories of cross-component issues that per-file validation misses: (1) description-rule conformance across all component files, (2) schema-code alignment between declared `inParams`/`outParams` and the embedded TypeScript that consumes them, (3) cross-component `objectType` reference resolution, (4) OData query pre-flight against connection schemas, (5) result-shape sync between a datasource's query options and its declared `outParams`. Triggers: "validate the project", "run cross-component validation checks", "lint the codebase", "find broken type references", "find OData pre-flight failures", "check the project before merge". For single-file audits use `component-validator` instead.
Trigger: done, complete, finish, before commit, quality check, verify. Run the project's own minimum quality scripts before claiming work is complete.