recursive-init

Generate or update AGENTS.md files for first-level package directories.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/antonio-ivanovski/agents-recursive-init --skill recursive-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recursive-init
Source: https://github.com/antonio-ivanovski/agents-recursive-init/tree/main/skills/recursive-init
Command: npx skills add https://github.com/antonio-ivanovski/agents-recursive-init --skill recursive-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize/update AGENTS.md for all first-level packages inside the provided directory, helping maintain concise package-level documentation in monorepos.

Core Features & Use Cases

  • Automatically identify all first-level subdirectories and generate or update each package's AGENTS.md
  • Spawn one per-package subagents to isolate work and enable parallel processing, with concurrency capped to five
  • Validate that every package receives an AGENTS.md and report the results to the user

Quick Start

Provide the path to the parent directory containing the first-level packages and run the recursive-init skill to generate or update AGENTS.md for each package.

Frequently Asked Questions about recursive-init

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

FAQPage Schema
How do I automatically generate AGENTS.md files for every package in a monorepo?

To automatically generate AGENTS.md files for every package in a monorepo, provide the parent directory path to automate initialization. The process enumerates first-level subdirectories and coordinates per-package subagents to create or update documentation concurrently.

What is the best way to maintain package-level documentation across multiple subdirectories?

The best way to maintain package-level documentation across multiple subdirectories is using automated subagent coordination. This approach isolates work per package, enables parallel processing capped at five concurrent agents, and validates that every package receives its required documentation file.

How many packages can be processed concurrently when initializing agent documentation?

A maximum of five packages can be processed concurrently when initializing agent documentation. The automation enforces this concurrency cap on per-package subagents to prevent resource exhaustion while parallelizing the generation of documentation files across first-level directories.

How do I verify that all packages in a directory have received an AGENTS.md file?

To verify that all packages have received an AGENTS.md file, the automation validates completion after subagents finish processing. It checks every first-level subdirectory and reports any missing package-level documentation files directly back to the user.

Does this automated initialization work with nested packages beyond the first level?

This automated initialization does not work with nested packages beyond the first level. It specifically enumerates and processes only first-level subdirectories inside the provided folder, ensuring concise package-level documentation is generated strictly for top-level monorepo packages.