orchestrator-code-quality

Analyze the orchestrator folder for duplication, complexity hotspots, and logging consistency.

3.8k|490|Updated Dec 11, 2025

Search Tags:#npm #logging #complexity #code-quality #duplication #orchestrator #lint

Ready to run

npx skills add https://github.com/DaKheera47/job-ops --skill orchestrator-code-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator-code-quality
Source: https://github.com/DaKheera47/job-ops/tree/main/.opencode/skills/code-quality
Command: npx skills add https://github.com/DaKheera47/job-ops --skill orchestrator-code-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintainers evaluate the quality of the orchestrator/ codebase by generating a focused, evidence-driven report on duplication, complexity hotspots, and logging consistency without changing code.

Core Features & Use Cases

Duplication detection and hotspots within the orchestrator/ folder
Complexity analysis identifying long functions and god modules
Logging and error-handling consistency checks across orchestrator boundaries
Use Case: Before a major refactor, run this skill to obtain a targeted improvement plan that can be executed in small, verifiable steps.

Quick Start

From the repository root, run the orchestrator code-quality check with npm run check:all in the orchestrator folder and review the produced report.

Frequently Asked Questions about orchestrator-code-quality

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

FAQPage Schema

How do I analyze code quality and find complexity hotspots in an orchestrator folder?▼

You can detect code duplication by running the orchestrator code-quality check with npm run check:all. This analyzes the orchestrator/ folder and produces a comprehensive report highlighting duplication hotspots and prioritized remediation steps.

What is the best way to check logging and error-handling consistency across orchestrator boundaries?▼

The best way to check logging consistency is using the orchestrator code-quality skill, which evaluates error-handling patterns across orchestrator boundaries. It uses npm run check:all as the gate to ensure tooling remains unaltered while providing evidence-based findings.

Can I generate a code quality report for a refactor without altering my existing npm lint tooling?▼

Yes, you can safely generate a code quality report without altering tooling. The skill operates read-only within the orchestrator scope, using npm run check:all to produce evidence-based findings and prioritized remediation steps without modifying your code.

Does the orchestrator code-quality check modify my source code during duplication analysis?▼

No, the orchestrator code-quality check does not modify source code during duplication analysis. It operates strictly within the repository scope to produce an evidence-driven report on complexity and logging consistency without changing existing files or tooling.