quality

Scan codebases for placeholders and enforce multi-stage quality gates before merging.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill quality-layerdynamics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/quality
Command: npx skills add https://github.com/LayerDynamics/Lore --skill quality-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures code meets high standards by scanning for and fixing incomplete implementations, stubs, and mocks, and by enforcing quality gates before shipping.

Core Features & Use Cases

  • Placeholder Detection: Identifies all forms of incomplete code, from TODO comments to language-native stubs.
  • Automated Remediation: Guides the process of fixing identified issues, prompting for user input when necessary.
  • Quality Gates: Implements a multi-stage review process including static analysis, spec compliance, and code quality checks before code can be merged.
  • Use Case: Before merging a new feature, use this Skill to automatically scan the codebase for any remaining stubs or incomplete logic, then run through a series of quality gates to ensure it's production-ready.

Quick Start

Use the quality skill to scan the current project for any placeholder code.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I scan my codebase for placeholder code and stub implementations before merging?

To scan for placeholder code and stub implementations, this tool automatically detects TODO comments, language-native stubs, and incomplete logic, then guides you through remediating each issue before merge readiness checks. It ensures code completeness through strict quality gates.

What is a multi-stage quality gate process for code review?

A multi-stage quality gate process enforces code standards by sequentially running static analysis, spec compliance checks, and code quality reviews before a branch can be merged. It prevents incomplete implementations, stubs, and mocks from reaching production environments.

How do I enforce code quality standards in CI/CD pipelines?

You can enforce code quality in CI/CD pipelines by integrating automated scanning that identifies incomplete code and triggers guided remediation. Strict quality gates then verify spec compliance and code completeness before allowing any merge to proceed.

Can I use automated remediation to fix incomplete code and TODO comments?

Yes, automated remediation identifies all forms of incomplete code, from TODO comments to stubs, and guides the fixing process. It prompts for user input when necessary to ensure verifiable implementation and adherence to strict code completeness rules.

What's the best way to detect mocks and stubs before a production release?

The best way to detect mocks and stubs before release is using an automated scanner that flags incomplete implementations and enforces multi-stage quality gates. This verifies that all code is complete, verifiable, and meets merge readiness standards.