claude_code_slash_commands 0.2.0 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 89ca4fe43efd662a0ead8fbc2638980bf11b1c087e1c67d2c8b8294e75af34b5
-  data.tar.gz: 7f137f9800fda4559099125496339ad688add88e40ff5ab4562434c9265d5679
+  metadata.gz: 604b553647bf6700a44f59a883cdf722996b1826fe1007ed458bf950d4108bbc
+  data.tar.gz: 33702b9349904328a854f23d5818a3843aa617cc320b155e9f211046317fbfc9
 SHA512:
-  metadata.gz: 39e56a72e6087ea9388136c7c8fda53af496a5a8cbafcd76f57e3abb8b3d40997a345562b81719ccd4260320fbbfc24dfafbcfa75eb651ad31b11d4f9e20d8b1
-  data.tar.gz: 48db40cc5f04f83e8cea64ce05149306c6584391bb3ba4275ed1b9e73a08324b55274469bd660b79117a5cd4a6e3bea93a036866b1cfc8b0f2d80c93aa8368da
+  metadata.gz: fa704f70f1fe4a49737134bcd9db8a97a7fbf3fee2e7169ae8f950e8281dfe050b7e439f78248637aefda49d71f9ac6605c5abee40802f609fef576ac33f1a07
+  data.tar.gz: ded25fc6aac37b2d88a378bbff51b16ca636b00928b0f63e10884369ae7f053eb337ed703aa3921cb14f01382f8ed6b24659c25f4a54cd82773d8f7b1d20c9e2

data/Gemfile.lock

@@ -1,12 +1,14 @@
 PATH
   remote: .
   specs:
-    claude_code_slash_commands (0.2.0)
+    claude_code_slash_commands (0.2.2)
+      base64
 
 GEM
   remote: https://rubygems.org/
   specs:
     ast (2.4.3)
+    base64 (0.3.0)
     date (3.4.1)
     erb (5.0.1)
     io-console (0.8.0)

data/README.md

@@ -1,6 +1,6 @@
 # claude_code_slash_commands
 
-This gem is for distributing Ruby-specific [slash commands](https://docs.anthropic.com/en/docs/claude-code/slash-commands) for [Claude Code](https://www.anthropic.com/claude-code).
+This gem is for distributing Ruby-specific [custom slash commands](https://docs.anthropic.com/en/docs/claude-code/slash-commands#custom-slash-commands) for [Claude Code](https://www.anthropic.com/claude-code).
 
 ## Prerequisites
 
@@ -56,6 +56,15 @@ This is useful for:
 
 Check the `commands/` directory to see what is available.
 
+### Safety
+
+Note that some commands have `allowed-tools` already defined, so Claude Code will not prompt you.
+I aim to restrict these to low risk tools such as git usage or web fetching, but you may wish to review before running.
+
+### Using the Commands
+
+In your Claude Code session, type `/ruby--`  and you will the list of available commands.
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/commands/ruby--add-rubocop.md

@@ -0,0 +1,19 @@
+---
+allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), WebFetch(domain:rubygems.org)
+description: Add rubocop
+---
+Add `rubocop` to this repo by following these steps:
+
+- Create a new branch
+- Check what the latest release of rubocop is using https://rubygems.org/gems/rubocop/
+- Add the latest release of the rubocop gem as a development dependency
+- Commit
+- If there is a `Rakefile`, configure the `rubocop` task
+- If there is a default task, configure `rubocop` to run as part of that
+- Commit
+- Run rubocop
+- If there are linting errors, run rubocop with the `--autocorrect` flag and commit
+- If the CLI suggests that additional errors can be fixed unsafely then run with `--autocorrect-all` and commit
+- If there are remaining linting errors, run rubocop with --auto-gen-config and commit.
+- If there is a CI configuration such as GitHub Actions, configure it to run rubocop as part of CI. The linting should be in a separate job from the tests.
+- Commit

data/commands/ruby--add-standard.md

@@ -0,0 +1,19 @@
+---
+allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), WebFetch(domain:rubygems.org)
+description: Add standard
+---
+Add `standardrb` to this repo by following these steps:
+
+- Create a new branch
+- Check what the latest release of standard is using https://rubygems.org/gems/standard/
+- Add the latest release of the standard gem as a development dependency
+- Commit
+- If there is a `Rakefile`, configure the `standard` task
+- If there is a default task, configure `standard` to run as part of that
+- Commit
+- Run standard
+- If there are linting errors, run standardrb with the `--fix` flag and commit
+- If the CLI suggests that additional errors can be fixed unsafely then run with `--fix-unsafely` and commit
+- If there are remaining linting errors, run standardrb with --generate-todo and commit.
+- If there is a CI configuration such as GitHub Actions, configure it to run standard as part of CI. The linting should be in a separate job from the tests.
+- Commit

data/commands/ruby--configure-gem-ci.md

@@ -0,0 +1,9 @@
+---
+description: Configure a gem's CI pipeline using GitHub Actions
+---
+The goal is to create a CI workflow file that runs the gem's tests as well as any linting or other verificiation tasks.
+
+- If no CI workflow file exists, create one, otherwise update the existing one.
+- Read https://www.ruby-lang.org/en/downloads/branches/ to check the latest Ruby release version.
+- Configure the CI matrix such that it covers the the minimum `required_ruby_version` in the `.gemspec`, as well as every minor release up to the latest Ruby version.
+- Commit

data/commands/ruby--update-ruby-version.md

@@ -0,0 +1,15 @@
+---
+description: Update to latest Ruby version
+---
+The goal is to update this project to use the latest Ruby version.
+
+- Before starting, verify the tests are passing (make a note of any deprecations)
+- Read https://www.ruby-lang.org/en/downloads/branches/ to check the latest Ruby release version.
+- If it's not already available, install that Ruby version.
+- Read https://www.ruby-lang.org/en/downloads/branches/ to check the latest Ruby release version.
+- If a .ruby-version file exists, update it to the latest Ruby version, otherwise create it.
+- Run `bundle install`.
+- If any gems are not compatible with the latest Ruby version, try update them.
+- Ensure the tests are still passing.
+- If there any new deprecations, ask if the user you should fix them.
+- Commit the changes.

data/exe/claude_code_slash_commands

@@ -1,6 +1,11 @@
 #!/usr/bin/env ruby
 
-require "bundler/setup"
+begin
+  require "bundler/setup"
+rescue LoadError
+  # Bundler not available or no Gemfile - just load the gem directly
+end
+
 require "claude_code_slash_commands"
 
 ClaudeCodeSlashCommands::CLI.start(ARGV)

data/lib/claude_code_slash_commands/installer.rb

@@ -4,6 +4,7 @@ require "fileutils"
 require "pathname"
 require "json"
 require "open3"
+require "base64"
 
 module ClaudeCodeSlashCommands
   class Installer
@@ -68,13 +69,19 @@ module ClaudeCodeSlashCommands
       target_file = @commands_target.join(filename)
 
       # Fetch the content of the command file
-      stdout, stderr, status = Open3.capture3("gh", "api", command["download_path"])
+      stdout, stderr, status = Open3.capture3(
+        "gh",
+        "api",
+        "repos/#{@repo}/contents/" + command["path"],
+        "--jq",
+        ".content"
+      )
 
       unless status.success?
         raise "Failed to fetch command content for #{filename}: #{stderr}"
       end
 
-      content = stdout
+      content = Base64.decode64(stdout)
 
       if target_file.exist?
         if target_file.read == content

data/lib/claude_code_slash_commands/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ClaudeCodeSlashCommands
-  VERSION = "0.2.0"
+  VERSION = "0.2.2"
 end

metadata

@@ -1,14 +1,28 @@
 --- !ruby/object:Gem::Specification
 name: claude_code_slash_commands
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.2
 platform: ruby
 authors:
 - Andy Waite
 bindir: exe
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
-dependencies: []
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: base64
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 email:
 - 13400+andyw8@users.noreply.github.com
 executables:
@@ -24,7 +38,10 @@ files:
 - LICENSE.txt
 - README.md
 - Rakefile
-- commands/configure-gem-ci.md
+- commands/ruby--add-rubocop.md
+- commands/ruby--add-standard.md
+- commands/ruby--configure-gem-ci.md
+- commands/ruby--update-ruby-version.md
 - exe/claude_code_slash_commands
 - lib/claude_code_slash_commands.rb
 - lib/claude_code_slash_commands/cli.rb

data/commands/configure-gem-ci.md

@@ -1,10 +0,0 @@
----
-description: Configure a gem's CI pipeline using GitHub Actions
----
-The goal is to create a CI workflow file that runs the gem's tests as well as any linting or other verificiation tasks.
-
-If no CI workflow file exists, create one, otherwise update the existing one.
-
- Read https://www.ruby-lang.org/en/downloads/branches/ to check the latest Ruby release version.
-
-Configure the CI matrix such that it covers the the minimum `required_ruby_version` in the `.gemspec`, as well as every minor release up to the latest Ruby version.