Agent Kit Updater
Use this skill when a repository already has Linear Agentic Kit installed and needs a version upgrade.
Trigger intent
- •
run agent-kit-updater - •
upgrade linear-agentic-kit to <VERSION> - •
update local kit from <OLD_VERSION> to <NEW_VERSION> - •
apply latest linear-agentic-kit updates
Minimal trigger support:
- •If user says only
run agent-kit-updater, treat it as:- •upgrade this repo to the latest kit version available in the source kit
- •auto-detect current version from target repo
VERSION - •run post-update
agent-kit-repo-adjuster - •return changed files and merge notes
Required workflow
- •Detect currently installed kit version from the target repo
VERSIONfile. - •Determine target version:
- •if user provided version, use it
- •otherwise use latest available source kit version
- •Compare installed version with the source kit version being applied.
- •Read source
CHANGELOG.mdand identify files touched since installed version. - •Update only touched kit-managed files:
- •root instructions (
AGENTS.md) - •
docs/** - •
.agents/skills/** - •
VERSION
- •root instructions (
- •Merge non-destructively. Preserve existing repo-specific constraints and local customizations.
- •Do not replace whole files when targeted edits or append/merge can preserve local guidance.
- •If touched files include templates with placeholders, resolve placeholders to repo-accurate values.
- •Run
agent-kit-repo-adjusterafter structural updates to ensure docs/skills remain repo-accurate. - •Verify no unresolved placeholders remain and no stale skill references exist.
- •Summarize what changed, what was intentionally left unchanged, and any manual follow-ups.
Minimum acceptance criteria
- •Installed
VERSIONin target repo matches the applied kit version. - •All changes map to entries in source
CHANGELOG.mdsince prior version. - •No repo-specific constraints were removed.
- •
docs/agent/skills.mdmatches actual installed skills.
Output contract
Always return:
- •previous installed version and new installed version
- •list of files updated
- •non-destructive merge notes for files with local customizations
- •verification summary (placeholder check + basic sanity checks)
- •residual follow-ups (if any)