Individual skill

code-changes

Change the user's own program, on their machine or through GitHub. Use when a request needs a change to the user's code (instrument tracing, wire the SDK, fix the agent behind a failing scenario, add a run parameter to a connected agent, version a hardcoded prompt) and not when the platform alone can do it (create a scenario, an evaluation, a prompt version, read traces).

skills/_compiled/native/code-changes/SKILL.md

Read pinned source

Source commit e5e4a1741ba26492ebf8865b24b05e0ef39b750e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
5,019
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Code changes

**Purpose**: Land a change in the user's program as a branch and a pull request, from a folder they share from their machine or through the LangWatch GitHub App.

**When to use**: the request changes the user's code. The decision table below says which requests do.

## Does this need code access?

| Request | Needs code | Why |
| --- | --- | --- |
| Instrument tracing, wire the SDK, add spans, capture metadata | yes | the change lives in their program |
| Fix the agent behind a failing scenario or a bad trace | yes | the behaviour lives in their program |
| Add or change a run parameter on a connected agent | yes | the parameter is declared in the connect call |
| Run a scenario against an account, plan, environment or fixture the connected agent does not accept yet | yes | the agent must declare the run parameter first; the scenario uses it afterwards |
Back to top