Skip to content

Rewrite julia-development skill around warm-session workflow - #5

Open
seabbs wants to merge 2 commits into
mainfrom
feat/julia-warm-session-workflow
Open

Rewrite julia-development skill around warm-session workflow#5
seabbs wants to merge 2 commits into
mainfrom
feat/julia-warm-session-workflow

Conversation

@seabbs

@seabbs seabbs commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Recentres the julia-development skill on the workflow that makes
agents good at Julia: keep a warm Julia session and verify each edit
with Revise and TestItemRunner, rather than testing once at the end.

Changes

  • Warm-session stance first (AgentREPL.jl under Claude Code, synchronous eval, PostToolUse reload nudge).
  • Corrected Revise section: struct/type edits reload on Julia 1.12+ with Revise 3.16+ and revise_structs, with the caveat that pre-existing objects keep the old type. Lists what still needs a fresh worker (macros, generated functions, alias-reached structs, polluted state).
  • TestItemRunner filter ladder (by file / name / tag) and a hot-versus-cold policy.
  • Trimmed the Documenter/Pluto-heavy material and the odd Pkg.add(; io=devnull) advice; kept the docstring/template guidance that still bites.

Net: 72 insertions, 315 deletions.

This was opened by a bot. Please ping @seabbs for any questions.

Recentre the skill on keeping a warm Julia session and verifying each
edit with Revise and TestItemRunner, replacing the earlier
end-of-run testing and Documenter/Pluto-heavy guidance.

Correct the Revise section: struct edits reload on Julia 1.12+ with
Revise 3.16+ and revise_structs, with the caveat that pre-existing
objects keep the old type. Add the TestItemRunner filter ladder and a
hot-versus-cold policy. Trim docstring guidance to the parts that
still bite.

Co-authored-by: Sam Abbott <contact@samabbott.co.uk>

## When to Use This Skill
Keep interface docstrings to a line or two and cross-reference
related methods with `See also: [`other`](@ref)` rather than

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nested backticks break this inline code span. See also: [other](@ref) parses as two separate code spans (See also: [ and ](@ref)) with other rendered as plain text, so the cross-reference syntax renders garbled. Wrap the whole example in double backticks to hold the inner backticks literally: See also: other .

Wrap the "See also" example in double backticks so the nested
`[`other`](@ref)` renders instead of splitting into two spans.
Soften the dependency note: a live session can Pkg.add then using,
with a restart only needed when the new package changes loaded code.

Co-authored-by: Sam Abbott <contact@samabbott.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants