quality-checklist

Enforce a code review checklist for Qt-like projects and generate a JSON report.

Updated Oct 25, 2025

Search Tags:#documentation #quality #lint #code-review #naming

Ready to run

npx skills add https://github.com/bartoszwarzocha/kalahari --skill quality-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-checklist
Source: https://github.com/bartoszwarzocha/kalahari/tree/main/.claude/skills/quality-checklist
Command: npx skills add https://github.com/bartoszwarzocha/kalahari --skill quality-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured code review quality checklist to ensure UI strings, icons, config, colors, logging, and documentation are consistent.

Core Features & Use Cases

Project Patterns: icons, UI strings, configuration, colors, logging checks
Code Quality: naming, comments, style, and test considerations
Documentation & Build: CHANGELOG, ROADMAP, OpenSpec alignment
Output: JSON-formatted decision summary

Quick Start

Apply the checklist to new changes and generate a JSON report for review.

Frequently Asked Questions about quality-checklist

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

FAQPage Schema

How do I standardize code reviews across my team?▼

Code reviews benefit from structured checklists enforcing consistent quality standards. This Skill provides a comprehensive quality checklist covering UI strings, icons, configuration, colors, logging, naming conventions, and documentation to ensure reviewers apply the same criteria across all changes.

What should I check for in code reviews besides functionality?▼

Beyond logic, reviewers should validate naming conventions, comments, documentation, UI resource consistency, localization strings, configuration values, color usage, logging calls, and changelog entries. This Skill systematizes those checks into an enforced pre-commit validation workflow.

Can I automate quality checks before commits?▼

Yes. Pre-commit validation enforces quality rules on icons, UI strings, configuration, colors, logging, and naming conventions before code reaches review. This Skill generates JSON-formatted reports documenting which checks passed or failed, reducing manual review overhead.

What codebases is this checklist designed for?▼

This checklist applies to codebases following Qt-like patterns with UI resources, localization, configuration management, and structured logging. It validates project-specific concerns like color palettes, icon standards, and build integrity alongside general code quality rules.

How do I document review decisions?▼

The Skill outputs a JSON-formatted decision summary capturing which quality checks were applied, their results, and alignment with project standards like OpenSpec or ROADMAP. This creates an auditable record of code review rationale.