code-quality-fix-all

Plan, validate, and apply code quality fixes from results.json on a dedicated branch.

617|397|Updated Oct 2, 2024
One-click install
npx skills add https://github.com/UKGovernmentBEIS/inspect_evals --skill code-quality-fix-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-fix-all
Source: https://github.com/UKGovernmentBEIS/inspect_evals/tree/main/.claude/skills/code-quality-fix-all
Command: npx skills add https://github.com/UKGovernmentBEIS/inspect_evals --skill code-quality-fix-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams systematically fix code quality issues detected during targeted topic reviews, reducing manual back-and-forth and ensuring consistent validation across changes.

Core Features & Use Cases

  • End-to-end fix orchestration: Plans, validates, and applies fixes for issues identified in a topic's code-quality review.
  • Topic-scoped execution: Operates on agent_artefacts/code_quality/<topic> directories, using results.json and README for guidance.
  • Validation-driven workflow: Includes validation, testing, and linting steps before changes are finalized.
  • Use Case: When a topic has multiple issues across evaluations, run this skill to apply fixes, run lightweight tests, and prepare a clean PR.

Quick Start

Use the skill against a topic path like agent_artefacts/code_quality/private_api_imports to begin planning and applying fixes.

Frequently Asked Questions about code-quality-fix-all

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

FAQPage Schema
How do I automate code quality fixes after a code review?

Automate code quality fixes by orchestrating an end-to-end workflow that reads review results, plans changes, validates with tests and linting, applies fixes on a dedicated branch, and documents outcomes for pull request preparation.

What is a validation-driven workflow for resolving lint and code review issues?

A validation-driven workflow for lint and code review issues enforces multi-phase execution: planning fixes, running lightweight tests and linting to validate changes, applying them on a dedicated branch, and performing a re-review before finalizing outcomes.

How do I apply topic-scoped code fixes using uv-based workflows?

Apply topic-scoped code fixes by targeting the agent_artefacts/code_quality/<topic> directory, reading results.json and README.md to plan fixes, validating changes with lightweight tests and linting, and applying them on a dedicated branch using standard Python tooling.

Do I need standard Python tooling to orchestrate code quality fixes?

Yes, you need standard Python tooling and the repository's uv-based workflow to orchestrate code quality fixes, as the workflow requires validating changes with lightweight tests and linting before applying them on a dedicated branch.

What's the best way to systematically resolve multiple issues found in a code-quality review?

Systematically resolve multiple code-quality review issues by orchestrating an end-to-end fix workflow that plans, validates, and applies changes on a dedicated branch, reducing manual back-and-forth and ensuring consistent validation across changes.

What are the limitations of automated code quality fix orchestration?

Automated code quality fix orchestration is limited to topic folders under agent_artefacts/code_quality/<topic> and requires pre-existing results.json and README.md files to plan fixes, meaning it cannot operate without a prior topic-specific code-quality review.