AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Wicked Garden Engineering Patch

skill-mikeparcewski-wicked-garden-patch · by mikeparcewski

|

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-mikeparcewski-wicked-garden-patch

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mikeparcewski-wicked-garden-patch)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
23d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Wicked Garden Engineering Patch? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

wicked-patch

Generate and propagate code changes across your entire codebase using the symbol graph.

All sub-actions run the patch CLI. The full invocation is:

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py"  [args]

Examples below abbreviate this to patch.py … — always run the full form.

The propagation diagram, quick-start recipes, per-action examples, the sample PROPAGATION PLAN / GENERATED PATCHES output, the patches-file JSON schema, and the language/type/SQL-dialect reference tables live in [refs/output-samples.md](refs/output-samples.md).

Sub-actions

| Sub-action | Purpose | |------------|---------| | patch-plan | Show what would be affected — propagation preview, no patches | | add-field | Add field with propagation | | rename | Rename across all usages | | remove | Remove field everywhere (DELETES code — see warning) | | apply | Apply saved patches from a JSON file | | new-generator | Author a new language generator ([refs/new-generator.md](refs/new-generator.md)) |

patch-plan — propagation preview

Show what would be affected by a change without generating patches. Distinct from the engineering domain skill's plan action (a human implementation plan with risks and tests) — patch-plan is the impact preview for mechanical patches. The CLI subcommand is plan.

Arguments: symbol_id (required — symbol to analyze); --change (add_field | rename_field | remove_field | modify_field); --depth (max traversal depth, default 5); --json (output as JSON).

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" plan "" --change "" [--json]

See [refs/output-samples.md](refs/output-samples.md) for examples and the sample PROPAGATION PLAN output.

add-field — add a field and propagate

Add a field to an entity/class and propagate to all affected files.

Arguments: symbol_id (required — e.g. path/Entity.java::EntityName); --name (required — field name); --type (required — String, Integer, Boolean, Date, etc.); --column (database column name, defaults to SNAKE_CASE of name); --label (UI label for form fields); --required (mark field non-nullable); --output/-o (save patches to JSON file); --apply (apply patches immediately); --verbose/-v (show full diffs).

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" add-field "" \
  --name "" \
  --type "" \
  [--column ""] \
  [--required] \
  [--verbose]

See [refs/output-samples.md](refs/output-samples.md) for examples, a JPA entity walkthrough (generated Java/SQL), and the GENERATED PATCHES output.

rename — rename a field/symbol across all usages

Arguments: symbol_id (required); --old (required — current field name); --new (required — new field name); --output/-o (save patches to file); --apply (apply patches immediately); --verbose/-v (show full diffs).

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" rename "" --old "" --new "" [--verbose]

What gets updated:

  • Field declarations
  • Getter/setter method names
  • Property references (this.oldNamethis.newName)
  • JSP EL expressions (${entity.oldName}${entity.newName})
  • Form bindings (path="oldName"path="newName")
  • TypeScript interfaces and type aliases
  • SQL column names (generates ALTER TABLE RENAME COLUMN)
  • Service layer references, and test files (with warning)

remove — remove a field and all its usages

Arguments: symbol_id (required); --field (required — field name to remove); --output/-o (save patches to file); --apply (apply patches immediately); --verbose/-v (show full diffs).

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" remove "" --field "" [--verbose]

Warning

This operation DELETES code. Always review patches before applying:

# Generate and save patches
patch.py remove SYMBOL --field foo -o patches.json

# Review
cat patches.json

# Apply when confident
patch.py apply patches.json

apply — apply patches from a saved JSON file

Arguments: patches_file (required — path to patches JSON file); --dry-run (show what would be done without applying).

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" apply "" [--dry-run]

See [refs/output-samples.md](refs/output-samples.md) for the save→review→dry-run→apply workflow and the patches-file JSON schema.

new-generator — create a new language generator

Create a new language generator for wicked-patch with scaffolding, golden test fixtures, and conformance validation. Arguments: language (required, e.g. "scala", "swift", "elixir"); framework (optional ORM/framework, e.g. "Slick", "CoreData", "Ecto"); extensions (optional file extensions, defaults to lowercase language). Follow the full 7-step authoring workflow (generator template with TYPE_MAP, __init__.py registration, golden fixture JSON, test_conformance.py additions, run tests, report) in [refs/new-generator.md](refs/new-generator.md).

Language & type reference

Supported languages (.java, .py, .ts/.js, .jsp, .sql), the generic→ per-language type mappings, and SQL dialect support (PostgreSQL / Oracle / MySQL / SQL Server, auto-detected or via --dialect) are tabulated in [refs/output-samples.md](refs/output-samples.md#language--type-reference).

Building the symbol database (wicked-estate)

wicked-patch reads a --db translated from the wicked-estate code graph (ADR 0005). Build the store, then translate it:

wicked-estate index . --db .codegraph/estate.db   # or reuse a crew-materialized store
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/estate_db.py" \
  [--estate-db .codegraph/estate.db] [--out .wicked/patch-symbols.db]

estate_db.py auto-discovers the store ($WICKED_ESTATE_DB, then .codegraph/estate.db, then .wicked-estate/graph.db); pass the resulting --db .wicked/patch-symbols.db to the patch sub-actions. Symbol ids keep the patch-native file::Name scheme (e.g. src/app.py::Order).

Safety Features

  • Dry-run by default: Shows patches without applying
  • Confirmation prompt: Asks before applying
  • Patch files: Save for review before applying
  • Warnings: Highlights test files and unsupported types
  • Reversible: Use git to undo

CLI Reference

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" --help
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" generators  # List supported languages

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.