What problem does it solve?
This Skill eliminates the wasted effort and broken continuous integration that result from implementing generic, misaligned quality improvements that don't match TajsOS's existing tooling, workflows, and project priorities.
Core Features & Use Cases
- Pragmatic quality improvements: Prioritizes small, scoped changes to CI, linting, test coverage, and code quality gates that align with the repo's current setup instead of broad, disruptive process overhauls.
- Tooling validation: Requires confirming existing commands, tools (like detekt/ktlint), and workflows are present and configured before proposing any changes, avoiding speculative quality gates that don't fit the project.
- Workflow hygiene: Ensures all new tools or workflow updates are documented with clear problem statements and verification steps, and prefers updating existing configurations over introducing parallel, conflicting systems.
- Use Case: For example, if you want to add a new code coverage check to TajsOS's CI pipeline, this skill guides you to first verify the existing test commands and coverage tools, then propose a small, scoped change that integrates with the current workflow instead of adding a separate, unconfigured tool.
Quick Start
Use the tajsos-repo-quality skill to review the current TajsOS CI workflows and propose a small, scoped lint improvement that matches the repo's existing detekt configuration.
