porting-agent-guidance

Ports agent guidance, skills, and auditors between sibling repositories with verified facts.

Updated May 9, 2020
One-click install
npx skills add https://github.com/avdi/purse --skill porting-agent-guidance-avdi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: porting-agent-guidance
Source: https://github.com/avdi/purse/tree/main/home/dot_agents/skills/porting-agent-guidance
Command: npx skills add https://github.com/avdi/purse --skill porting-agent-guidance-avdi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When two repos in the same org accumulate agent guidance at different rates, one drifts behind the other. Copying the richer repo's skills wholesale imports facts that are false in the target — wrong paths, missing gems, capabilities CI doesn't actually have — producing guidance that confidently misleads every downstream agent. ## Core Features & Use Cases - Delta-driven porting: Dates the last port from the target's own commits, then diffs the source with rename detection (-M10%) to find real content changes instead of rename noise. - Fact re-grounding: Verifies every path, gem, script, and CI capability claim against the target repo before including it, cutting what the target lacks and rewriting examples in the target's vocabulary. - Scope and landing coordination: Settles scope tiers, branch/PR strategy, and naming conventions with the user up front, then lands the port as standards-only commits with updated indexes and validated frontmatter. - Use Case: A project's .claude/ directory has fallen behind a sibling repo's. Use this Skill to find what the source added since the last port, adapt each artifact to the target's real facts, discover areas the source has no counterpart for, and land the refresh on the existing PR branch. ## Quick Start Port the agent guidance and skills from our sibling repo into this project, adapting everything to this repo's actual setup.

Frequently Asked Questions about porting-agent-guidance

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

FAQPage Schema
How do I port agent skills from one repo to another?

Date the last port from the target's commits, diff the source repo from that cutoff with rename detection, then adapt each artifact by verifying every fact against the target. Never copy wholesale — the source supplies structure and lessons, the target supplies facts.

How to find what changed in a repo's .claude directory since a date?

Use git rev-list -1 --before=<date> main to find the cutoff commit, then git diff --stat -M10% against main filtered to .claude and AGENTS.md. The -M10% flag detects renames so renamed skills don't appear as delete-plus-add noise.

Can I clone a GitHub repo without SSH keys in a devcontainer?

Yes, clone over HTTPS using the token already in the environment: git clone with https://x-access-token:${GH_TOKEN}@github.com/org/repo. Check gh auth status first to confirm the token exists rather than debugging SSH keys.

Why does a copied skill give wrong advice in the target repo?

Copied skills carry the source repo's facts — paths, gems, CI capabilities — that may not exist in the target. Capability claims like "CI keeps the failure screenshot" are especially risky; verify each one in the target's CI config and initializers.

When should I not port an auditor skill to another repo?

Don't port an auditor without its paired standards skill in the target — it will invent rules. The generalist auditor is the sole deliberate exception to this rule.