import_from 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 777b908c81a5507f9af5c24b5eec7502fc52297e33ad931f9b2ad79df07b035b
+  data.tar.gz: da800d07e43cd948f8586d01c89fda200fcad7c439449a9e04ce31ec8dc2a0ec
+SHA512:
+  metadata.gz: 87e839ff2eb2a7dc29415bf320c00e5f7e2818ba52b0fb8bad8c5f5110bf876d871f531827f0264533ad3bea55c6fd4b4dcd55193158416451013ae1f115ab3a
+  data.tar.gz: fb8c4d83b55f00f7d68300ab2fb9a4a8d6c2965d93e1513fac27f07be4d94294a0d7112e83074056b9de460b77762ce1cad6d55363c57c4da676a818b0dd72dc

data/.claude/commands/document.md

@@ -0,0 +1,105 @@
+# Document
+
+Generates documentation for Ruby code using YARD with 100% coverage enforcement.
+
+## Commands
+
+Generate documentation:
+```bash
+bundle exec rake yard
+```
+
+Format YARD comments:
+```bash
+bundle exec rake yard:format
+```
+
+Verify 100% documentation coverage:
+```bash
+bundle exec rake verify_measurements
+```
+
+Check for documentation quality issues:
+```bash
+bundle exec rake yard:junk
+```
+
+Generate coverage report:
+```bash
+bundle exec rake yardstick_measure
+```
+
+## Configuration
+
+Requires `.yardstick.yml` in project root with 100% threshold:
+```yaml
+threshold: 100
+rules:
+  ApiTag::Presence: { enabled: true }
+  ApiTag::Inclusion: { enabled: true }
+  ApiTag::ProtectedMethod: { enabled: true }
+  ApiTag::PrivateMethod: { enabled: true }
+  ExampleTag: { enabled: true }
+  ReturnTag: { enabled: true }
+  Summary::Presence: { enabled: true }
+  Summary::Delimiter: { enabled: true }
+```
+
+## Coverage Report
+
+After running measurement, check detailed line-by-line issues:
+```bash
+cat measurements/report.txt
+```
+
+Report shows specific file, line number, method, and documentation issues that need fixing.
+
+## Documentation Standards
+
+### Required Tags
+- Every public/private method, class, and module requires `@api public` or `@api private`
+- All parameters: `@param name [Type] Description`
+- All returns: `@return [Type] Description` (use `[void]` if no return)
+- Examples required for all public methods: `@example Description`
+- Error conditions: `@raise [ExceptionClass] When this occurs`
+
+### Type Notation
+- Use `String` not `string`
+- Arrays: `Array<String>` for string arrays
+- Hashes: `Hash{String=>Object}` for hash types
+- Use `Boolean` not `bool`, `Integer` not `int`
+- Nullable types: `String, nil` or `String|nil`
+
+### Formatting Rules
+- Blank lines required between YARD tag groups
+- Exception: `@param` and `@option` tags can be grouped together
+- Wrap class/method names in `+` markers: `+PrivateKey+`
+- Cross-reference related methods: `@see #other_method`
+
+### Documentation Structure
+```ruby
+# Brief one-line summary ending with period.
+#
+# @api public
+#
+# @example Description of example
+#   code_example
+#   result # => expected_output
+#
+# @param name [Type] Description
+# @param other [Type] Other description  
+#
+# @return [Type] Description
+#
+# @raise [ExceptionClass] When this exception occurs
+#
+def method_name
+end
+```
+
+## Integration
+
+Documentation verification is included in the quality assurance pipeline:
+```bash
+bundle exec rake qa
+```

data/.claude/commands/gemfile/update.md

@@ -0,0 +1,52 @@
+---
+allowed-tools: Bash(bundle :*), Bash(git :*), Read, Edit, MultiEdit, Glob
+description: Update Gemfile dependencies to latest minor versions
+argument-hint: [gemfile] [commit]
+---
+
+Update the dependencies in the specified Gemfile (or ./Gemfile if no path provided) to their latest minor versions while
+preserving major version constraints. Only update MAJOR.MINOR versions, never PATCH versions unless explicitly needed.
+
+Steps:
+1. Read the Gemfile at the specified path (or ./Gemfile if $ARGUMENTS is empty)
+2. Read the corresponding Gemfile.lock to get current resolved versions
+3. Run `bundle outdated --only-explicit` to check for available minor updates of explicitly declared gems
+4. For each gem in Gemfile, check if Gemfile.lock has a newer minor version than the current Gemfile constraint allows
+5. Update gem version constraints to match the minor version from Gemfile.lock or latest available, whichever is newer (MAJOR.MINOR format)
+6. Use pessimistic version constraints (~> MAJOR.MINOR) to prevent automatic patch updates
+7. Preserve any existing version operators but ensure they follow minor-only update strategy
+8. Run `bundle update` to apply the changes
+7. Skip step 8, 9 and 10 if --commit flag is not provided
+8. Stage Gemfile (only if not gitignored)
+9. Verify if Gemfile.lock is tracked and not gitignored. If both conditions are met, stage it for commit.
+10. Create a git commit with message 'Update development dependencies' and a description listing all updated gems with their old and new versions like:
+
+<commit-message>
+  Updated gems:
+- rubocop: 1.75.2 → 1.78.0
+- rubocop-yard: 0.10.0 → 1.0.0
+</commit-message>
+
+11. If any dependencies were updated, respond only with the update message. And if the user has chose to commit,
+include the update commit message. Otherwise, respond only with the no op message.
+
+<update-message>
+Updated gems:
+- rbs: 3.8 → 3.9
+- rubocop: 1.78 → 1.80
+- rubocop-rspec: 3.6 → 3.7
+
+<update-commit-message>The changes have been committed with the message "Update development dependencies".</update-commit-message>
+</update-message>
+
+<no-op-message>All dependencies are up to date.</no-op-message>
+
+Key bundle outdated flags used:
+- `--only-explicit`: Only show gems explicitly listed in Gemfile (not dependencies)
+- No `--local` flag to ensure remote gem sources are checked for latest versions
+
+Arguments:
+- `gemfile`: Gemfile path (defaults to ./Gemfile if not provided)
+- `--commit`: Create a git commit after updating dependencies with message 'Update development dependencies' and a description listing all updated gems with their old and new versions
+
+Gemfile path: ${ARGUMENTS:-./Gemfile}