PHPackages                             asernohq/llm-devtools - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [CLI & Console](/categories/cli)
4. /
5. asernohq/llm-devtools

ActiveProject[CLI & Console](/categories/cli)

asernohq/llm-devtools
=====================

Small, pragmatic developer tools for LLM-assisted coding workflows.

v1.0.0.0(1mo ago)00MITPHPPHP >=8.2

Since May 9Pushed 2w agoCompare

[ Source](https://github.com/asernohq/llm-devtools)[ Packagist](https://packagist.org/packages/asernohq/llm-devtools)[ Docs](https://github.com/asernohq/llm-devtools)[ RSS](/packages/asernohq-llm-devtools/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (1)DependenciesVersions (2)Used By (0)

LLM DevTools
============

[](#llm-devtools)

Small, pragmatic developer tools for LLM-assisted coding workflows.

This repository contains tools for extracting compact source context, preparing prompts, and reducing hallucination risk when working with large language models on real codebases.

Why this exists
---------------

[](#why-this-exists)

LLMs are most useful when they receive the right context.

They are also most dangerous when they receive almost the right context.

This repository exists to make it easier to give coding assistants precise, compact, and project-aware source context without dumping an entire codebase into a prompt.

The goal is not to replace the developer. The goal is to make the developer faster while keeping the boring-but-important details visible.

Status
------

[](#status)

Early utility repository.

The tools are intentionally practical and lightweight. APIs, names, and file layout may change while the toolkit is still young.

Requirements
------------

[](#requirements)

Requirements may vary by tool.

Typical requirements:

- A recent PHP CLI runtime.
- Local source code checkouts.
- A terminal or shell suitable for developer workflows.

Tools in this repository are primarily designed for local development workflows.

Installation
------------

[](#installation)

Clone the repository:

```
git clone https://github.com/asernohq/llm-devtools.git
cd llm-devtools
```

Use the relevant tool directly from the repository, or follow the usage notes in the tool itself.

Suggested local layout
----------------------

[](#suggested-local-layout)

The tools work best when source repositories live in predictable local structures.

Example:

```
C:\dev\www\vendor-or-org\project-a
C:\dev\www\vendor-or-org\project-b
C:\dev\www\vendor-or-org\project-c

```

Deterministic local paths make it easier to extract focused context without scanning unrelated projects.

Usage
-----

[](#usage)

Each tool should provide its own help output or usage notes.

General pattern:

```
php path/to/tool.php --help
```

Many tools are expected to print Markdown or plain text that can be pasted directly into LLM chats, coding agents, issue descriptions, or documentation drafts.

On Windows, output can often be copied directly to the clipboard:

```
php path\to\tool.php [options] | clip
```

Output format
-------------

[](#output-format)

Tools should prefer simple, structured output.

Good output formats include:

- Markdown.
- Plain text.
- JSON, when intended for other tools.
- Line-oriented output for shell workflows.

When output is intended for LLM prompts, it should be compact, explicit, and easy to paste.

Example structure:

```
# Context

## path/to/source-file.php

```php