update-agents-core

Merges upstream agents-core scaffolding updates into the current project via npx or git.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill update-agents-core-cristoslc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-agents-core
Source: https://github.com/cristoslc/LLM-personal-agent-patterns/tree/main/L3-agents-core/.agents/skills/update-agents-core
Command: npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill update-agents-core-cristoslc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects that import shared agent scaffolding (.agents/ directory, AGENTS.md, CLAUDE.md) from an upstream repository drift out of date over time, and manually syncing files risks losing local customizations or creating messy merge conflicts. ## Core Features & Use Cases - Dual update paths: Uses npx skills add as the preferred update mechanism and falls back to a pure git fetch/merge workflow when npx is unavailable. - Incremental merges: Creates real merge commits with --allow-unrelated-histories so subsequent updates only diff the delta since the last update instead of the entire upstream history. - Conflict resolution policy: Accepts upstream versions unconditionally for upstream-owned files (.agents/, import script) while reconciling AGENTS.md to preserve local routing rules and sections. - Quick check mode: Runs only the diff steps to report what changed upstream without applying anything. - Use Case: A team member notices the shared scaffolding repo added new skills; they invoke this skill to fetch, merge, review the staged diff, and commit the update safely. ## Quick Start Ask the agent to update the agents-core scaffolding from upstream and report what changed before committing.

Frequently Asked Questions about update-agents-core

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

FAQPage Schema
How do I update my .agents directory from the upstream repository?▼

Invoke the update skill, which first tries npx skills add for skill updates, then fetches the agents-upstream remote and merges it with git. It shows you the staged diff before committing so you can review changes.

How do I check for scaffolding updates without applying them?▼

Use the quick check mode, which runs only the preflight, fetch, and diff steps. It reports what changed upstream and stops, letting you run the full update later when ready.

What happens if the agents-upstream git remote is missing?▼

The skill detects the missing remote during verification and stops. It shows the exact git remote add command for the upstream repository and asks you to re-invoke the skill after adding it.

Will updating overwrite my local AGENTS.md customizations?▼

No. AGENTS.md conflicts are reconciled by preserving local routing rules and sections while accepting upstream changes to upstream-owned sections. Files under .agents/ are upstream-owned and always accept the upstream version.

Why does the update use a merge commit instead of squash?▼

A real merge commit records the merge base, so future updates only diff the delta since the last update. Squash merges record no base, forcing every update to diff the entire upstream history and causing broader conflicts.

Can I undo the update if the merge goes wrong?▼

Yes. Run git merge --abort at any point before committing to restore the working tree to its pre-merge state. The skill also requires a clean working tree upfront to make recovery straightforward.