harnesscp-loop

Audits, fixes, validates, and logs improvements to VS Code Copilot harnesses.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LSDIPPOLLC/harness-cp --skill harnesscp-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harnesscp-loop
Source: https://github.com/LSDIPPOLLC/harness-cp/tree/main/.github/skills/harnesscp-loop
Command: npx skills add https://github.com/LSDIPPOLLC/harness-cp --skill harnesscp-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from maintaining a VS Code Copilot harness by turning improvement into a repeatable audit-improve-validate-log cycle.

Core Features & Use Cases

  • Weakest-Pillar Targeting: Finds the lowest-scoring harness pillar and prioritizes the highest-leverage fix first.
  • Iterative Improvement Workflow: Routes work to the right atomic skill, applies the change, then re-scores to confirm progress.
  • Continuity Across Sessions: Reads and writes improvement logs so future sessions can resume where the last one stopped.
  • Use Case: After an audit shows weak hooks or missing memory, use this Skill to systematically raise the score one pillar at a time until the harness is solid.

Quick Start

Use the harnesscp-loop skill to audit your current Copilot harness, improve the weakest pillar, validate the result, and record the change.

Frequently Asked Questions about harnesscp-loop

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

FAQPage Schema
How do I continuously improve my VS Code Copilot harness?

To continuously improve your VS Code Copilot harness, use an audit, fix, validate, and log loop that systematically targets and remediates the weakest configuration pillars. This repeatable cycle ensures iterative maintenance and progressive refinement of your setup.

What is the best way to fix weak Copilot context, memory, or hooks?

The best way to fix weak Copilot context, memory, or hooks is to apply weakest-pillar targeting, which identifies the lowest-scoring harness component and routes the fix to the highest-leverage area first. This ensures systematic score improvements across your configuration.

How does a Copilot harness audit loop maintain session continuity?

A Copilot harness audit loop maintains session continuity by reading and writing persistent improvement logs after each validation check. This allows future sessions to resume the iterative refinement process exactly where the previous session stopped.

Can I systematically remediate Copilot routing and permissions after an audit?

Yes, you can systematically remediate Copilot routing and permissions after an audit by routing the identified weaknesses to the appropriate atomic skills. The workflow applies the change, validates the result, and logs the update for continuous refinement.

When should I use an iterative improvement workflow for Copilot ergonomics?

You should use an iterative improvement workflow for Copilot ergonomics during post-audit remediation and continuous refinement. It is necessary when pillar scoring reveals gaps in gates, permissions, or routing that require persistent change logging to support ongoing maintenance.