# claudekit mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für claudekit in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:claudekit
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install claudekit
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:claudekit
- **Paketmanager:** Homebrew
- **Version:** 0.9.5
- **Quellzusammenfassung:** Intelligent guardrails and workflow automation for Claude Code
- **Homepage:** <https://github.com/carlrannaberg/claudekit>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- claudekit (Alias)
- claudekit-hooks (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.9.5
## Projektgeschichte und Nutzung

claudekit is a Claude Code companion toolkit that packages hooks, slash commands, guardrails, checkpoints, and specialist agent prompts for AI-assisted software development workflows.

### Projektgeschichte

The project is organized as an npm-installed command-line toolkit with a GitHub documentation tree. Its README presents the project around Claude Code setup, hook execution, code review commands, checkpoint commands, and prompt extraction for external LLM tools.

### Adoptionsgeschichte

The package is distributed through npm-style global installation and Homebrew, which puts it in the same CLI-tool culture as other developer workflow helpers. The official README also surfaces npm version/download badges and notes inclusion in an Awesome Claude Code list.

### Wie es verwendet wird

Typical use starts with installing `claudekit`, running `claudekit setup`, and then using Claude Code slash commands and automatic hooks for review, validation, file guarding, and checkpoint workflows.

### Warum Paket-Nerds sich dafür interessieren

Package-manager users care because claudekit turns a set of Claude Code conventions into a reproducible CLI install: commands, hooks, project/user configuration files, and generated prompt assets can be installed and inspected like normal developer tooling.

### Related projects

- The README explicitly positions claudekit alongside Claude Code and codebase-map, and it references optional MCP integration with Context7.

### Quellen

- Official GitHub README: describes claudekit as guardrails/workflow automation for Claude Code, documents npm installation, setup commands, hooks, and config files.
- Official GitHub docs directory: provides the dedicated documentation surface.


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .claude/settings.json, .claudekit/config.json, .claude/settings.local.json, ~/.claude/settings.json

## Combined YAML source

View the package source record on GitHub. [combined/claudekit.yml](https://github.com/mxcl/pkgdb/blob/main/combined/claudekit.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph