kinit

Generate an AGENTS.md file documenting project components, commands, and conventions.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/kkestell/skills --skill kinit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kinit
Source: https://github.com/kkestell/skills/tree/main/plugins/k/skills/kinit
Command: npx skills add https://github.com/kkestell/skills --skill kinit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It creates a concise, up‑to‑date AGENTS.md file that documents a project's components, commands, and conventions, giving new contributors a quick orientation.

Core Features & Use Cases

  • Explores the repository to infer the tech stack, major codebase sections, and essential build/run/test commands.
  • Generates AGENTS.md from a template, customizing content based on the discovered information.
  • Offers optional configuration of ~/.k access for downstream skills.
  • Prompts the user to review and adjust the generated document before it is saved.

Quick Start

Run kinit pointing to the repository root to generate an AGENTS.md overview.

Frequently Asked Questions about kinit

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

FAQPage Schema
How do I automatically generate an AGENTS.md file to orient new contributors?

To generate an AGENTS.md file, run kinit pointing at your repository root. It reads manifests like README and Makefile to infer the tech stack, codebase map, and commands, then drafts the orientation document for your review before saving.

What is the best way to document a project's tech stack and build commands from existing files?

Documenting a project's tech stack and commands is done by reading language-specific manifests and configuration files. The extracted information is compiled into a structured AGENTS.md file that outlines components, conventions, and essential build or test commands.

Can I customize the generated AGENTS.md content before it is saved to my codebase?

Yes, you can customize the generated AGENTS.md content. The tool prompts you to review and adjust the discovered tech stack details, codebase sections, and commands before the final orientation document is written to your repository.

Does generating orientation documentation require any external dependencies or tools?

Generating orientation documentation requires no external dependencies. The tool operates independently by directly reading repository files like READMEs, Makefiles, and language manifests to infer the project structure and create the AGENTS.md overview.

When should I initialize or refresh documentation for an existing codebase?

You should refresh documentation for an existing codebase when major components, commands, or conventions change. Running the initialization process updates the AGENTS.md file to reflect the current tech stack and ensures new contributors receive an accurate orientation.

Why use an automated codebase orientation generator instead of manually writing project documentation?

Using an automated orientation generator prevents manual documentation from becoming stale. It automatically extracts the tech stack and codebase map from source manifests, ensuring the AGENTS.md file always provides a concise, up-to-date overview for new contributors.