skills.rest
hoklims
hoklimsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

oco-verify-fix

Run build, type, lint, and test commands to validate code changes.

Updated Mar 24, 2026
Search Tags:#testing#verification#code-quality#ci#impact-analysis
One-click install
npx skills add https://github.com/hoklims/oco --skill oco-verify-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oco-verify-fix
Source: https://github.com/hoklims/oco/tree/main/oco-plugin/skills/oco-verify-fix
Command: npx skills add https://github.com/hoklims/oco --skill oco-verify-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps developers validate their code modifications by automatically running build, type checking, linting, and testing processes to ensure correctness and stability.

Core Features & Use Cases

  • Automated Verification Workflow: Detects project type and runs appropriate verification commands like build, type check, lint, and tests.
  • Impact Analysis: Checks whether impacted functions are covered by tests using MCP tools, identifying potential regression risks.
  • Use Case: Developers modify code files and want an automated tool to confirm that their changes do not break the build or tests before merging.

Quick Start

Invoke the verification process to automatically run build, type check, linting, and testing steps on your project.

Frequently Asked Questions about oco-verify-fix

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

FAQPage Schema
How do I automate code verification before merging changes?▼

Code verification detects your project type and automatically executes build, type checking, linting, and testing commands. This validates modifications to ensure correctness and stability before merging.

How does impact analysis identify regression risks in modified functions?▼

Impact analysis identifies regression risks by checking whether functions modified by code changes are covered by tests using MCP tools. It evaluates test coverage to prevent potential regressions in software engineering workflows.

Can I integrate automated code verification into CI pipelines?▼

Yes, automated code verification is suitable for CI pipelines. It validates code changes by executing build, type, lint, and test commands, and assesses test coverage of modified functions to prevent regressions during continuous integration.

What commands does an automated verification workflow run for code changes?▼

An automated verification workflow runs build, type check, lint, and test commands. It detects the project type to determine the appropriate verification commands for ensuring code changes do not break the build or tests.

Do I need MCP tools to perform impact analysis on test coverage?▼

Yes, impact analysis requires integration with MCP tools to check whether impacted functions are covered by tests. This integration identifies potential regression risks by assessing test coverage of modified code.

Related Skills

Explore More Software Engineering Skills→
xu-xiangxu-xiang
1.8k

springboot-verification

Automate Spring Boot verification with builds, tests, coverage, and security scans.

Community
Advanced
atomicinnovationatomicinnovation
30

test-coverage-lens

Assess test coverage and testing strategy for code changes.

Official
Intermediate
RheasilviaRheasilvia

Review Changes

Analyze code changes for risk and test coverage via knowledge graph.

Community
Advanced
samChang72samChang72
1

verification-loop

Execute automated build, type, lint, test, security, and diff checks on Claude Code sessions.

Community
Advanced