<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/README.md, branch add-plugin/xcode</title>
<subtitle>Official Claude Code plugin directory
</subtitle>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/'/>
<entry>
<title>code-modernization: count failures and the machine's python, once per version</title>
<updated>2026-09-25T19:06:43+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T19:06:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=c8874f5ad883e26428f483ffa4d537cc81489e64'/>
<id>c8874f5ad883e26428f483ffa4d537cc81489e64</id>
<content type='text'>
Usage counts now say what the plugin runs on (system, python status and version, path problems) and which kind of failure happens: a missing or placeholder python, a permission block, a model error, or an error in the plugin's own script. Failures are classified on the machine into a fixed list and only the code is sent, once per kind per session. A session-start ping, once per plugin version, counts machines where nobody gets as far as typing a command. When python cannot run, the shell wrapper reports that itself, and on Windows it falls back to python or the py launcher.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Usage counts now say what the plugin runs on (system, python status and version, path problems) and which kind of failure happens: a missing or placeholder python, a permission block, a model error, or an error in the plugin's own script. Failures are classified on the machine into a fixed list and only the code is sent, once per kind per session. A session-start ping, once per plugin version, counts machines where nobody gets as far as typing a command. When python cannot run, the shell wrapper reports that itself, and on Windows it falls back to python or the py launcher.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: version 1.0.0, usage counts and a README results table</title>
<updated>2026-09-25T18:29:00+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T18:29:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=363af43603ecdb1bdbed7303764b6daeeec7c37f'/>
<id>363af43603ecdb1bdbed7303764b6daeeec7c37f</id>
<content type='text'>
The plugin now has a version and a changelog. Two hooks record whole-number usage counts (which command ran, how far a system got, how many rules and proofs) through the CLI's own telemetry: counts from 100 up are rounded, nothing is sent when the plugin is not in use, and any of three switches turns it off. The README documents every key and lists what the plugin was tried on, checked against the run files.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The plugin now has a version and a changelog. Two hooks record whole-number usage counts (which command ran, how far a system got, how many rules and proofs) through the CLI's own telemetry: counts from 100 up are rounded, nothing is sent when the plugin is not in use, and any of three switches turns it off. The README documents every key and lists what the plugin was tried on, checked against the run files.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: call workflows by name and fix the uplift version arguments</title>
<updated>2026-09-25T03:27:49+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:27:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=f33999b153851d927a103e0f4b6032ed53a94aad'/>
<id>f33999b153851d927a103e0f4b6032ed53a94aad</id>
<content type='text'>
The Workflow tool refuses a plugin script path whenever the plugin lives
outside the working directory, which is the normal case for an installed
plugin: the model failed once or twice on every run before falling back to
the registered name. The commands now call each workflow by its registered
name and mention the script path only as a fallback.

modernize-uplift also referred to legacy/$system_version, which is not an
argument; it now uses $source_version everywhere, and the version pair, the
rewrite target and the vision fall back to analysis/&lt;system&gt;/INTENT.md when
they are not given. The README notes that a scripted (claude -p) run needs
CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS=0 so long fan-out steps can finish.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Workflow tool refuses a plugin script path whenever the plugin lives
outside the working directory, which is the normal case for an installed
plugin: the model failed once or twice on every run before falling back to
the registered name. The commands now call each workflow by its registered
name and mention the script path only as a fallback.

modernize-uplift also referred to legacy/$system_version, which is not an
argument; it now uses $source_version everywhere, and the version pair, the
rewrite target and the vision fall back to analysis/&lt;system&gt;/INTENT.md when
they are not given. The README notes that a scripted (claude -p) run needs
CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS=0 so long fan-out steps can finish.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: a front door that asks what you want once</title>
<updated>2026-09-25T03:18:45+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:18:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=b6b148f496e8da208676b4a1553bdf292ce340d9'/>
<id>b6b148f496e8da208676b4a1553bdf292ce340d9</id>
<content type='text'>
/code-modernization:modernize takes no arguments. It finds the code, asks
what the person wants to do with it (a newer version of the same
technology, a rewrite in another one, a rebuild, or just to understand it)
and what must stay true, writes the answers to analysis/&lt;system&gt;/INTENT.md,
shows the road ahead in a few lines, and gives the exact first command.
On a return visit it acts like status.

brief takes its objective, target and each phase's build command from
INTENT.md, and uplift, transform and reimagine fall back to it for their
versions, target and vision, so nobody is asked the same thing twice. The
README's start section now begins with the front door.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
/code-modernization:modernize takes no arguments. It finds the code, asks
what the person wants to do with it (a newer version of the same
technology, a rewrite in another one, a rebuild, or just to understand it)
and what must stay true, writes the answers to analysis/&lt;system&gt;/INTENT.md,
shows the road ahead in a few lines, and gives the exact first command.
On a return visit it acts like status.

brief takes its objective, target and each phase's build command from
INTENT.md, and uplift, transform and reimagine fall back to it for their
versions, target and vision, so nobody is asked the same thing twice. The
README's start section now begins with the front door.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: simpler commands, a source option, a report page and an equivalence check</title>
<updated>2026-09-25T03:14:51+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:14:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=cafefb304bde4070c6c0877528ee49c1252eff85'/>
<id>cafefb304bde4070c6c0877528ee49c1252eff85</id>
<content type='text'>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: add an optional live progress pane</title>
<updated>2026-09-25T01:11:07+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T01:07:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=c9e990089c6c87cb96e227e998edbada1df82861'/>
<id>c9e990089c6c87cb96e227e998edbada1df82861</id>
<content type='text'>
Adds a hooks module, off unless the CLI's early-access function hooks
are enabled, that draws a pane beside the transcript while the commands
run: the system, which steps are done, a map of its code, each unit of
work and where it stands, what needs attention, and the next command.

It reads only the artifacts the commands write and the legacy tree, so
it works for any language and for a rewrite, a same-stack uplift or a
greenfield rebuild. The map comes from topology.json when there is one
and from the source tree when there is not. In an uplift each module is
set against the baseline; tests are read from JUnit XML, .trx reports or
the runs a session sees; a button shows and hides the pane, and
/modernize-panel does the same from the keyboard.

The same module adds x-ray context on legacy reads, a review deck for
business rules (/modernize-review), a sign-off dialog (/modernize-sign)
and a fleet view that spots one failure repeating across agents. It
only watches: it never blocks, rewrites or restores an edit, and it runs
no program inside the trees it reads. An uplift's changed modules are
found by comparing the working copy with the tree by file name and size
through the file API. Its options are the plugin's userConfig. Without
the flag nothing loads and the commands, agents and workflows behave as
before.

91 tests in tests/ run with "claude plugin test"; plugin validate
passes on the release build with the flag on and off.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adds a hooks module, off unless the CLI's early-access function hooks
are enabled, that draws a pane beside the transcript while the commands
run: the system, which steps are done, a map of its code, each unit of
work and where it stands, what needs attention, and the next command.

It reads only the artifacts the commands write and the legacy tree, so
it works for any language and for a rewrite, a same-stack uplift or a
greenfield rebuild. The map comes from topology.json when there is one
and from the source tree when there is not. In an uplift each module is
set against the baseline; tests are read from JUnit XML, .trx reports or
the runs a session sees; a button shows and hides the pane, and
/modernize-panel does the same from the keyboard.

The same module adds x-ray context on legacy reads, a review deck for
business rules (/modernize-review), a sign-off dialog (/modernize-sign)
and a fleet view that spots one failure repeating across agents. It
only watches: it never blocks, rewrites or restores an edit, and it runs
no program inside the trees it reads. An uplift's changed modules are
found by comparing the working copy with the tree by file name and size
through the file API. Its options are the plugin's userConfig. Without
the flag nothing loads and the commands, agents and workflows behave as
before.

91 tests in tests/ run with "claude plugin test"; plugin validate
passes on the release build with the flag on and off.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: fix contradictions and stale references in existing text</title>
<updated>2026-09-25T00:50:21+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T05:32:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=65b0f06f1bd6309b88ca8c3cc92e34d7a4f51f5f'/>
<id>65b0f06f1bd6309b88ca8c3cc92e34d7a4f51f5f</id>
<content type='text'>
Make the text say what the commands and workflows already do: where each build command writes, which commands need earlier output, the approval stop before an uplift fan-out, a version placeholder that named arguments left unusable, a reference to a README section that does not exist, and a few counts and step references. No new steps or options.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Make the text say what the commands and workflows already do: where each build command writes, which commands need earlier output, the approval stop before an uplift fan-out, a version placeholder that named arguments left unusable, a reference to a README section that does not exist, and a few counts and step references. No new steps or options.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: extract-rules asks before a large run, with an estimate</title>
<updated>2026-09-25T00:50:21+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T02:52:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d13ff0324cf9a8744be6c75251689816485e68cf'/>
<id>d13ff0324cf9a8744be6c75251689816485e68cf</id>
<content type='text'>
The command told the model to state the shard count and an estimate
before launching, but in live runs on a small system it launched
without saying anything: a reply that only mentions the estimate is
easy to skip and is not a gate.

With more than 12 shards the command now requires an AskUserQuestion
that carries the shard count, the line count and the estimate (agents,
tokens, minutes) and offers to run all shards, run only a slice, or
cancel. With 12 shards or fewer it launches straight away and says
what it launched.

The estimate is now a working formula (10 to 15 agents per shard, about
16k tokens per agent, about 8 agents finishing per minute) with the two
runs it comes from: 4 shards used 58 agents in under 10 minutes, and a
44-program, 30,000-line estate used 466 to 647 agents.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The command told the model to state the shard count and an estimate
before launching, but in live runs on a small system it launched
without saying anything: a reply that only mentions the estimate is
easy to skip and is not a gate.

With more than 12 shards the command now requires an AskUserQuestion
that carries the shard count, the line count and the estimate (agents,
tokens, minutes) and offers to run all shards, run only a slice, or
cancel. With 12 shards or fewer it launches straight away and says
what it launched.

The estimate is now a working formula (10 to 15 agents per shard, about
16k tokens per agent, about 8 agents finishing per minute) with the two
runs it comes from: 4 shards used 58 agents in under 10 minutes, and a
44-program, 30,000-line estate used 466 to 647 agents.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: README section on teams, adapting the plugin and what it has been tried on</title>
<updated>2026-09-25T00:50:21+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T02:22:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=6f020b9f66a1340efeab2fd4ca7a17f348e3fea9'/>
<id>6f020b9f66a1340efeab2fd4ca7a17f348e3fea9</id>
<content type='text'>
Adds one section to the README for the questions a team asks before
adopting the plugin. It says who owns which directory and which
artifact suits which reviewer, taken from what each command says the
artifact contains, and that state lives in files so a second person or
a fresh session can pick up with modernize-status.

It notes that preflight and assess write their reports under analysis/
(with two side effects: preflight's smoke test builds one small project
with the system's own tools, and a non-git project's credential
inventory goes to ~/.modernize/), that the commands, agents and workflows are plain
markdown and JavaScript that can be forked, and that extraction is
model-driven, so BUSINESS_RULES.md is reviewed output rather than a
deterministic build artifact.

It also lists the prerequisites (accept-edits mode or the allow rules,
and a toolchain for the target stack) and says that the one example the
README shows is AWS CardDemo, so stacks without an example should expect
to adapt the prompts.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adds one section to the README for the questions a team asks before
adopting the plugin. It says who owns which directory and which
artifact suits which reviewer, taken from what each command says the
artifact contains, and that state lives in files so a second person or
a fresh session can pick up with modernize-status.

It notes that preflight and assess write their reports under analysis/
(with two side effects: preflight's smoke test builds one small project
with the system's own tools, and a non-git project's credential
inventory goes to ~/.modernize/), that the commands, agents and workflows are plain
markdown and JavaScript that can be forked, and that extraction is
model-driven, so BUSINESS_RULES.md is reviewed output rather than a
deterministic build artifact.

It also lists the prerequisites (accept-edits mode or the allow rules,
and a toolchain for the target stack) and says that the one example the
README shows is AWS CardDemo, so stacks without an example should expect
to adapt the prompts.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: preflight checks that legacy/ is protected from edits</title>
<updated>2026-09-25T00:50:20+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T02:20:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=9b4e3c21f27766422e43259da71745b863684784'/>
<id>9b4e3c21f27766422e43259da71745b863684784</id>
<content type='text'>
The commands are written never to edit legacy/, but nothing checked
that anything enforced it. Preflight now has a Check 7 that reads,
without changing anything, the project's .claude/settings.json and
.claude/settings.local.json and the user's settings file, and looks for
an Edit deny rule that covers legacy/. The result is a row in
PREFLIGHT.md with the same status marks as the other checks: a green row
names the file and the rule, and a warning prints the settings snippet
to add. The check never edits a settings file and never suggests
loosening one.

The check also says plainly that a permission rule covers the file tools
and the shell commands the CLI recognizes, not a script that
opens the files itself, so a green row is not a guarantee. A read-only
mount, or a sandbox that blocks writes to legacy/, is. The README no
longer says the settings file enforces the invariant: the commands keep
to it by convention and the rule backs that up.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The commands are written never to edit legacy/, but nothing checked
that anything enforced it. Preflight now has a Check 7 that reads,
without changing anything, the project's .claude/settings.json and
.claude/settings.local.json and the user's settings file, and looks for
an Edit deny rule that covers legacy/. The result is a row in
PREFLIGHT.md with the same status marks as the other checks: a green row
names the file and the rule, and a warning prints the settings snippet
to add. The check never edits a settings file and never suggests
loosening one.

The check also says plainly that a permission rule covers the file tools
and the shell commands the CLI recognizes, not a script that
opens the files itself, so a green row is not a guarantee. A read-only
mount, or a sandbox that blocks writes to legacy/, is. The README no
longer says the settings file enforces the invariant: the commands keep
to it by convention and the rule backs that up.
</pre>
</div>
</content>
</entry>
</feed>
