Skip to main content

Style-aware code generation — analyze any codebase and generate new code that matches its style

Project description

 __  __        ____          _
|  \/  |_   _ / ___|___   __| | ___
| |\/| | | | | |   / _ \ / _` |/ _ \
| |  | | |_| | |__| (_) | (_| |  __/
|_|  |_|\__, |\____\___/ \__,_|\___|
        |___/

Style-aware code generation. Analyze any codebase to extract its coding style, then generate new code that matches it exactly.


What it does

MyCode learns how a developer or team writes code — naming conventions, type annotation style, import grouping, docstring format, error handling patterns — and uses that style profile to generate new code that feels like it was written by the same hand.

It is built to slot into larger agentic systems: the analyzer and generator are clean library functions, and the backend is swappable (local LLM, Claude, or OpenAI).


Requirements

  • Python 3.10+
  • A running AI backend (see Backends)

Installation

# Clone and install in editable mode
git clone <repo-url>
cd MyCode
pip install -e .

# For Claude backend support
pip install -e ".[claude]"

# For OpenAI backend support
pip install -e ".[openai]"

# For all backends
pip install -e ".[all]"

The my-code CLI command is registered automatically on install.


Backends

MyCode delegates inference to a pluggable backend. Choose one based on what you have available.

Backend Flag Requirement
Local LLM --backend llama (default) MCP server running at localhost:8000
Anthropic Claude --backend claude ANTHROPIC_API_KEY env var or --api-key
OpenAI --backend openai OPENAI_API_KEY env var or --api-key
Custom MCP server --backend mcp Any MCP server at --mcp-url

Setting up a local LLM

The llama backend expects an MCP server at http://localhost:8000/mcp that exposes two tools: one for code generation and one for analysis. Any MCP-compatible wrapper around a local model will work. Here is a recommended setup using llama.cpp:

1. Download a model

A code-focused model works best. Good options:

Download a .gguf quantized file (Q4_K_M is a good balance of size and quality).

2. Start the llama.cpp server

# Install llama.cpp (or use a pre-built binary)
pip install llama-cpp-python[server]

# Start the OpenAI-compatible server
python -m llama_cpp.server \
  --model ./models/codellama-7b-instruct.Q4_K_M.gguf \
  --host 0.0.0.0 \
  --port 8000 \
  --n_ctx 4096

3. Wrap it with an MCP server

The llama backend communicates over MCP, not directly with the llama.cpp HTTP API. You need a thin MCP wrapper that exposes two tools:

  • A code generation tool (name must not contain "analyze")
  • An analysis tool (name must contain "analyze")

Both tools accept a query string and return the model's completion. A minimal FastMCP wrapper example:

# llm_mcp_server.py
from fastmcp import FastMCP
import requests

mcp = FastMCP("local-llm")
LLM_URL = "http://localhost:8000/v1/completions"

def _complete(prompt: str) -> str:
    resp = requests.post(LLM_URL, json={
        "prompt": prompt,
        "max_tokens": 1024,
        "temperature": 0.1,
    })
    return resp.json()["choices"][0]["text"]

@mcp.tool()
def generate_code(query: str) -> str:
    return _complete(query)

@mcp.tool()
def analyze_code(query: str) -> str:
    return _complete(query)

if __name__ == "__main__":
    mcp.run(transport="streamable-http", host="0.0.0.0", port=8000)
pip install fastmcp
python llm_mcp_server.py

4. Point MyCode at it

my-code --backend llama --ricky-url http://localhost:8000/mcp analyze .

Or set a custom URL if your server runs on a different port:

my-code --backend llama --ricky-url http://localhost:9000/mcp analyze .

CLI Usage

Step 1 — Analyze a codebase

Point MyCode at any directory. It reads every .py file and builds a style profile.

my-code analyze ./path/to/codebase

With verbose output:

my-code analyze ./path/to/codebase --verbose

Using a different backend:

my-code --backend claude analyze ./path/to/codebase
my-code --backend openai --api-key sk-... analyze ./path/to/codebase

The profile is saved to style_profile.json by default. Specify a different path with --profile:

my-code analyze ./path/to/codebase --profile ./profiles/my_team.json

Step 2 — Generate code

my-code generate "write a function that parses a CSV file and returns a list of dicts"

MyCode loads style_profile.json and instructs the backend to produce code that matches the analyzed style — naming, annotations, docstrings, structure and all.

# Use a specific profile
my-code generate "write a retry decorator" --profile ./profiles/my_team.json

# Use Claude to generate
my-code --backend claude generate "write a binary search function"

# Override the model
my-code --backend claude --model claude-sonnet-4-6 generate "write a rate limiter"

CLI Reference

my-code [OPTIONS] COMMAND

Options:
  --backend {llama,claude,openai,mcp}   AI backend to use (default: llama)
  --api-key TEXT                         API key for claude/openai backends
  --model TEXT                           Override the default model
  --ricky-url TEXT                       Local LLM MCP server URL (default: http://localhost:8000/mcp)
  --mcp-url TEXT                         Custom MCP server URL (default: http://localhost:8001/mcp)
  --profile TEXT                         Path to style profile JSON (default: style_profile.json)

Commands:
  analyze PATH    Analyze a codebase and write a style profile
    --verbose     Print each file as it is analyzed

  generate TASK   Generate code matching the saved style profile

Python API

MyCode is a first-class library. All CLI functionality is available programmatically.

from my_code import StyleAnalyzer, generate_code, make_backend
from pathlib import Path

# Create a backend
backend = make_backend()                           # local LLM (default)
backend = make_backend("claude")                   # Claude (reads ANTHROPIC_API_KEY)
backend = make_backend("openai", api_key="sk-...") # OpenAI

# Analyze a codebase
analyzer = StyleAnalyzer(backend)
profile = analyzer.analyze_codebase(Path("./my_project"), verbose=True)

# Save and reload the profile
StyleAnalyzer.save_profile(profile, Path("style.json"))
profile = StyleAnalyzer.load_profile(Path("style.json"))

# Generate code
code = generate_code(
    task="write a function that validates an email address",
    backend=backend,
    profile=profile,
)
print(code)

Bring your own backend

Implement AIBackend to connect any model:

from my_code import AIBackend, StyleAnalyzer, generate_code

class MyBackend(AIBackend):
    max_file_chars = 4000  # how much of each file to send for analysis

    def ask_for_code(self, prompt: str) -> str:
        # call your model, return the generated code as a string
        ...

    def ask_to_analyze(self, prompt: str) -> str:
        # call your model, return a JSON string describing the style
        ...

backend = MyBackend()
analyzer = StyleAnalyzer(backend)
profile = analyzer.analyze_codebase(Path("."))
code = generate_code("write a logging helper", backend, profile)

Deep Analysis

For a richer style profile, scripts/deep_analyze.py runs six focused queries (naming, error handling, string formatting, module structure, docstrings, and representative snippets) and synthesizes them into a single detailed profile.

# Run from the project root; writes style_profile.json
python scripts/deep_analyze.py

This is slower than the standard analyze command but produces a more detailed profile, which leads to better code generation.


Running Tests

python tests/test_library.py

The test suite uses a MockBackend so no live AI backend is required. It exercises the full analyze → generate pipeline.


Project Structure

my_code/
├── analyzer.py          # StyleAnalyzer — scans files, builds style profile
├── generator.py         # generate_code() — formats prompt and calls backend
├── ricky_client.py      # Low-level MCP client for the local LLM server
├── cli.py               # CLI entry point (my-code command)
├── backends/
│   ├── base.py          # AIBackend abstract base class
│   ├── ricky_backend.py # Local LLM backend (connects via MCP)
│   ├── claude_backend.py
│   ├── openai_backend.py
│   └── mcp_backend.py   # Placeholder for custom MCP backends
└── utils/
    └── prompts.py       # Prompt templates for extraction, summary, generation
scripts/
└── deep_analyze.py      # Multi-query deep style analysis
tests/
└── test_library.py      # Smoke tests (no live backend required)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mycode_aiagent-0.1.0.tar.gz (16.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mycode_aiagent-0.1.0-py3-none-any.whl (14.7 kB view details)

Uploaded Python 3

File details

Details for the file mycode_aiagent-0.1.0.tar.gz.

File metadata

  • Download URL: mycode_aiagent-0.1.0.tar.gz
  • Upload date:
  • Size: 16.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.4

File hashes

Hashes for mycode_aiagent-0.1.0.tar.gz
Algorithm Hash digest
SHA256 c337e20d8b092d23df6ba3cf380cca277d3172a32ba195386297ecfaaf65c8d7
MD5 8e5aae90189fda9a52ffb31285f45875
BLAKE2b-256 a1c21714ca8b11ffae59e53feaf5efa95dbf49bef1d6a672d5b39dacf2e5aa2d

See more details on using hashes here.

File details

Details for the file mycode_aiagent-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: mycode_aiagent-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 14.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.4

File hashes

Hashes for mycode_aiagent-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 e8f3007955c3c07e4e5836d891f825a2e5ef5991532fe25858b74d8967c27d48
MD5 d258bf020b9c42eb93b7c32808e7eee7
BLAKE2b-256 e90a53c6dc8b540a23de399f20b60c16be5944ea15f00d732a93766a87b68640

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page