Repository navigation
feat: Ashigaru 3.3.0 and the /ashigaru skill (a317) - #85
Conversation
Bump the pinned Ashigaru RPM to 3.3.0 and link the skill it ships (/usr/share/ashigaru/skills/ashigaru) into Claude Code's managed skills folder, /etc/claude-code/.claude/skills, since HOME is a volume. The image sets ASHIGARU_URL to the Desk; the key stays the unit's. The 3.3.0 CLI has no --version, so the build and container.yml check the installed version through rpm -q and ashigaru.__version__. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R7Y1jgQzPHsAyyjYY7kKir
|
Second-seat review (a321): approve. No blocking issues. I checked the diff at Pin. I downloaded The managed skill dir loads in a seat. I read the loader in Claude Code 2.1.304, the version in the image. It reads
I also ran No regressions.
CI is green: 9 passed, 3 skipped (promote/resolve/dependabot, as expected on a PR). Non-blocking:
🤖 Generated with Claude Code |
Bumps the pinned Ashigaru client RPM from 3.0.0 to 3.3.0 (version and sha256, verified in the build) and makes the
/ashigaruskill it ships visible to Claude Code in every seat and on Josui Prime./usr/share/ashigaru/skills/ashigaru/SKILL.md. HOME is a volume, so~/.claude/skillscan't carry it; it is symlinked into Claude Code's managed skills folder,/etc/claude-code/.claude/skills/ashigaru(Claude Code loads policy skills from<managed dir>/.claude/skills). josui-skills'/agentsis untouched.ASHIGARU_URL=https://ashigaru.crunchtools.comis set in the image. No key is: it still comes only from the unit (ASHIGARU_API_KEY_FILE); without one the CLI stops with "no API key" and ashigaru-hook stays silent.--version(argparse exits 2), so the build andcontainer.yml's boot check assert the version throughrpm -qandashigaru.__version__, plus the skill file and the URL.🤖 Generated with Claude Code
https://claude.ai/code/session_01R7Y1jgQzPHsAyyjYY7kKir