mcpField
C
code-execution

code-execution

github.com/mhattingpeteDevelopment689290 installsUpdated 14w ago
Repository

About code-execution

A Claude Code skill for running Python-based file, code, transformation, and Git operations locally. It is intended for bulk or multi-step work and returns summaries rather than large source-data results.

Key features

  1. 01Filesystem copy and edit operations
  2. 02Code metadata and dependency analysis
  3. 03Batch code transformations
  4. 04Git status and change operations
  5. 05Local bulk processing

Use cases

  1. 01Refactor identifiers across many files
  2. 02Move selected functions between files
  3. 03Audit dependencies across a codebase

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill code-execution

After installing, type/code-executionin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

examples/
bulk_refactor.py
codebase_audit.py
extract_functions.py

Details

From the project README

Code Execution

Execute Python locally with API access. 90-99% token savings for bulk operations.

When to Use

  • Bulk operations (10+ files)
  • Complex multi-step workflows
  • Iterative processing across many files
  • User mentions efficiency/performance

How to Use

Use direct Python imports in Claude Code:

from execution_runtime import fs, code, transform, git

# Code analysis (metadata only!)
functions = code.find_functions('app.py', pattern='handle_.*')

# File operations
code_block = fs.copy_lines('source.py', 10, 20)
fs.paste_code('target.py', 50, code_block)

# Bulk transformations
result = transform.rename_identifier('.', 'oldName', 'newName', '**/*.py')

# Git operations
git.git_add(['.'])
git.git_commit('feat: refactor code')

If not installed: Run ~/.claude/plugins/marketplaces/mhattingpete-claude-skills/execution-runtime/setup.sh

Available APIs

  • Filesystem (fs): copy_lines, paste_code, search_replace, batch_copy
  • Code Analysis (code): find_functions, find_classes, analyze_dependencies - returns METADATA only!
  • Transformations (transform): rename_identifier, remove_debug_statements, batch_refactor
  • Git (git): git_status, git_add, git_commit, git_push

Pattern

  1. Analyze locally (metadata only, not source)
  2. Process locally (all operations in execution)
  3. Return summary (not data!)

Examples

Bulk refactor (50 files):

from execution_runtime import transform
result = transform.rename_identifier('.', 'oldName', 'newName', '**/*.py')
# Returns: {'files_modified': 50, 'total_replacements': 247}

Extract functions:

from execution_runtime import code, fs

functions = code.find_functions('app.py', pattern='.*_util$')  # Metadata only!
for func in functions:
    code_block = fs.copy_lines('app.py', func['start_line'], func['end_line'])
    fs.paste_code('utils.py', -1, code_block)

result = {'functions_moved': len(functions)}

Code audit (100 files):

from execution_runtime import code
from pathlib import Path

files = list(Path('.').glob('**/*.py'))
issues = []

for file in files:
    deps = code.analyze_dependencies(str(file))  # Metadata only!
    if deps.get('complexity', 0) > 15:
        issues.append({'file': str(file), 'complexity': deps['complexity']})

result = {'files_audited': len(files), 'high_complexity': len(issues)}

Best Practices

✅ Return summaries, not data ✅ Use code_analysis (returns metadata, not source) ✅ Batch operations ✅ Handle errors, return error count

❌ Don't return all code to context ❌ Don't read full source when you need metadata ❌ Don't process files one by one

Token Savings

FilesTraditionalExecutionSavings
105K tokens50090%
5025K tokens60097.6%
100150K tokens1K99.3%

Comments

Markdown supported