arn-infra-refresh

Refresh project-local infrastructure reference files with live online research.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-infra-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-infra-refresh
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-infra/skills/arn-infra-refresh
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-infra-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates refreshing project-local infrastructure reference files by fetching the latest tool versions, MCP packages, and IaC patterns through online research to keep a project up to date.

Core Features & Use Cases

  • Automated reference refresh: pull current versions for registries, IaC patterns, container patterns, CI/CD patterns, cloud patterns, and infra guides, and write them to the local .arness/infra-references/ directory with provenance.
  • Change detection: compare local references against official sources and flag breaking changes or deprecations.
  • Audit trail: record source URLs and timestamps in the reference checksums manifest for traceability.

Quick Start

Run a full refresh of infrastructure references using online research to pull the latest versions and update the local overrides.

Frequently Asked Questions about arn-infra-refresh

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

FAQPage Schema
How do I automate refreshing infrastructure reference files with latest versions?

Automating infrastructure reference refresh involves pulling current tool versions, MCP packages, and IaC patterns via online research and writing updates to the .arness/infra-references/ directory with provenance tracking.

What is the best way to keep IaC patterns and cloud patterns current across projects?

Keeping IaC patterns and cloud patterns current requires comparing local references against official online sources, flagging breaking changes or deprecations, and recording source URLs with timestamps in a reference checksums manifest.

How does change detection work when updating infra references?

Change detection for infra references works by comparing local project files against official sources to identify version mismatches, flag breaking changes, and highlight deprecations before applying any updates.

Does refreshing infra references overwrite my existing local changes?

Refreshing infra references preserves existing user changes by default, only overwriting local files when explicitly triggered by a refresh action, ensuring manual edits remain intact unless a full overwrite is intended.

Can I track where updated infrastructure references came from?

Tracking reference provenance is handled by recording source URLs and timestamps in the .reference-checksums.json manifest, providing a full audit trail for traceability across registries, container patterns, and CI/CD patterns.

What infrastructure patterns can I refresh using online research?

Refreshing infra references covers registries, IaC patterns, container patterns, CI/CD patterns, cloud patterns, and infrastructure guides, pulling the latest versions for each into per-project local overrides.