self-improvement

Coordinate framework-wide ARF file updates across specs, tests, and docs.

16|8|Updated Apr 15, 2026

Search Tags:#testing #versioning #infrastructure #framework #coordination #arf

Ready to run

npx skills add https://github.com/GliteTech/glite-arf --skill self-improvement-glitetech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/GliteTech/glite-arf/tree/main/arf/skills/self-improvement
Command: npx skills add https://github.com/GliteTech/glite-arf --skill self-improvement-glitetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and execute a framework-wide change across every related ARF file — specifications, verificators, aggregators, skills, scripts, hooks, tests, materializers, and docs — in a dedicated infrastructure branch and worktree with style checks and the full test suite.

Core Features & Use Cases

Orchestrates end-to-end updates across arf/, arf/specifications, and related style guides to maintain consistency.
Coordinates version bumps, spec_version updates, and tooling changes while preserving isolation and traceability.
Applies to framework-level modifications such as adding or updating a skill, verificator, or materializer, ensuring changes are tested and reviewed in a dedicated infra worktree.

Quick Start

Describe the intended framework change and let the skill map all impacted components and orchestrate the update.

Frequently Asked Questions about self-improvement

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

FAQPage Schema

How do I coordinate framework-wide ARF changes across specifications and tests?▼

Framework-wide ARF changes are coordinated by mapping impacted components like specifications, verificators, aggregators, scripts, and tests to keep everything in sync within a dedicated infrastructure branch and worktree.

What is the best way to keep ARF specifications, verificators, and docs in sync during updates?▼

Keeping ARF specifications, verificators, aggregators, scripts, and docs in sync requires orchestrating end-to-end updates across arf/ directories while enforcing style-guide and testing workflows in an isolated infrastructure worktree.

How do I manage version bumps in SKILL.md and spec_version updates for data formats?▼

Version bumps in SKILL.md and spec_version updates in data formats are managed by applying framework-level modifications to arf/ and meta/ boilerplate, ensuring changes are tested and reviewed in a dedicated infra worktree.

Can I use infrastructure worktrees to isolate and test framework-level modifications?▼

Infrastructure worktrees isolate and test framework-level modifications by applying boilerplate changes to arf/ and meta/ directories, orchestrating version bumps, and enforcing style checks with the full test suite before review.

Do I need to run style checks and the full test suite when updating arf/ boilerplate?▼

Updating arf/ boilerplate requires running style checks and the full test suite to ensure framework-wide consistency across specifications, verificators, aggregators, skills, scripts, hooks, materializers, and docs.

What are the limitations of coordinating framework-wide changes across ARF files?▼

Coordination across ARF files is limited to arf/ directories and generic parts of meta/ boilerplate, meaning modifications outside these framework-level boundaries or unrelated to specifications, verificators, and aggregators are not managed by this process.