integrate-project

Audit an existing codebase and integrate the agent harness without disrupting current conventions.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/PVMalove/claude-agent-harness --skill integrate-project-pvmalove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integrate-project
Source: https://github.com/PVMalove/claude-agent-harness/tree/main/global-skills/integrate-project
Command: npx skills add https://github.com/PVMalove/claude-agent-harness --skill integrate-project-pvmalove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting an AI agent harness into a mature repository risks overwriting existing conventions, CI setups, and AI-tool configurations. This Skill audits what the repository already knows about itself before installing anything, so integration happens without silent conflicts or guesswork. ## Core Features & Use Cases - Read-only codebase audit: Derives the real stack, commands, branch conventions, and CI behavior directly from manifests, lockfiles, and workflow files rather than README claims. - Conflict detection: Finds existing AI-tool configuration (AGENTS.md, CLAUDE.md, .cursor/rules, copilot instructions) and surfaces conflicts for the owner to reconcile instead of overwriting them. - Optional decision-history reconstruction: Recovers architectural decisions from PR/MR history and session logs, grading each as CONFIRMED, INFERRED, or UNKNOWN, and drafts ADRs only after explicit owner authorization. - Use Case: A team with a two-year-old TypeScript monorepo wants to adopt the agent harness. The Skill audits package.json scripts and GitHub Actions, flags an existing CLAUDE.md that conflicts with harness conventions, confirms findings with the owner, then hands off to the standard install flow. ## Quick Start Ask the agent to integrate the harness into this existing repository and audit its current setup first.

Frequently Asked Questions about integrate-project

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

FAQPage Schema
How do I integrate an AI agent harness into an existing repository?▼

Run a read-only audit first: read package manifests, lockfiles, and CI workflow files to derive the real stack and commands, then check for existing AI-tool configs like AGENTS.md or CLAUDE.md. Confirm findings with the owner before installing anything.

When should I use integrate-project instead of start-project?▼

Use integrate-project when the repository already has meaningful code, conventions, CI, or existing AI-tool configuration. Use start-project for brand-new ideas, empty repositories, or projects that already have the harness installed.

Does the audit phase modify any files in my repository?▼

No. The audit phase is strictly read-only: it writes nothing, installs nothing, and selects no capability. Even the optional ADR reconstruction writes no files until the owner reviews the closing report and explicitly authorizes which ADRs to write.

What happens if my project already has a CLAUDE.md or AGENTS.md?▼

Existing AI-tool instructions are read and compared against harness conventions. Any conflict is reported to the owner as a finding to reconcile, never silently overwritten.

How are reconstructed architecture decisions graded for confidence?▼

Each decision is graded CONFIRMED when code, merged PRs, or reviews directly support it, INFERRED when combined sources imply it, or UNKNOWN when no source supports it. Merged diffs and current code outrank session proposals when sources conflict.