lcea
lcea is the short name for the project formerly called llm-code-edit-applier.
The shorter name is used for the package and CLI command so it is easier to type and remember.
This project provides:
- a minimal diff-like edit format for LLM output
- a prompt template that constrains model output to that format
- a robust applier that parses, validates, and applies edits to a workspace
Minimal edit format
Each edit targets one file and uses a single fenced block:
path/to/file.py
```edit
<<<<<<< SEARCH
old text
=======
new text
>>>>>>> REPLACE
Rules:
- The line before the fenced block is the relative file path.
- Fence info string must be `edit`.
- `SEARCH` is matched literally.
- `REPLACE` is the replacement text.
- Empty `SEARCH` means create at file start when the file already exists, or create a new file.
- Empty `REPLACE` means delete the matched text.
- A `SEARCH` block must match exactly once in the target file unless `SEARCH` is empty.
## Prompt template
See `src/llm_edit_applier/prompts.md`.
## Run tests
```bash
python -m pytest
CLI
After installation:
lcea spec
lcea prompt
lcea apply edits.txt --root .
cat edits.txt | lcea apply --root .
1 maintainer
Metadata
1 maintainer
Release files for lcea 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| lcea-0.1.0.tar.gz | 6.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lcea-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / lcea-0.1.0.tar.gz
| Download URL | lcea-0.1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2af388e33c0a90d05c17dd54366e1eb2bf0fd2378f90fb1803bcdb825e597fad
|
|
BLAKE2b-256 checksum How to use checksums |
5ac889bd087aa0a0b5ffeef28523df7ebe49d14f2577261d38bfe8a6ceb3fdd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.
Transparency logRelease files / lcea-0.1.0-py3-none-any.whl
| Download URL | lcea-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a913a374611d18c346380adba334f3c713cd805bcdc4364b2a37d4ff85e5d89
|
|
BLAKE2b-256 checksum How to use checksums |
aa5715489632b37ffd9b62180c09f22a2280ac5dee4cfa9c07bdb00639de61c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.
Transparency logSecurity for lcea 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lcea-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
