bug_bunny 4.8.0 → 4.8.1

data/skill/references/testing.md

@@ -0,0 +1,138 @@
+# Testing
+
+## Estructura
+
+```
+spec/
+├── spec_helper.rb
+├── support/
+│   ├── bunny_mocks.rb          # Stubs para unit tests
+│   └── integration_helper.rb   # Helpers para integration tests
+├── unit/                       # Sin RabbitMQ real
+│   ├── configuration_spec.rb
+│   ├── client_session_pool_spec.rb
+│   ├── consumer_spec.rb
+│   ├── session_spec.rb
+│   ├── consumer_middleware_spec.rb
+│   ├── controller_after_action_spec.rb
+│   ├── observability_spec.rb
+│   └── resource_attributes_spec.rb
+└── integration/                # Requiere RabbitMQ
+    ├── client_spec.rb
+    ├── consumer_middleware_spec.rb
+    ├── controller_spec.rb
+    ├── error_handling_spec.rb
+    ├── infrastructure_spec.rb
+    └── resource_spec.rb
+```
+
+## Unit Tests — Mocking de Bunny
+
+Los unit tests usan `BunnyMocks` para evitar dependencia de RabbitMQ:
+
+```ruby
+# spec/support/bunny_mocks.rb
+BunnyMocks::FakeChannel     # Simula canal Bunny
+BunnyMocks::FakeConnection  # Simula conexión Bunny
+```
+
+Patrón de uso:
+
+```ruby
+let(:connection) { BunnyMocks::FakeConnection.new }
+let(:session) { BugBunny::Session.new(connection) }
+```
+
+Para Producer: `allow_any_instance_of(BugBunny::Producer).to receive(:rpc).and_return(response)`
+
+## Integration Tests — Helpers
+
+### with_running_worker
+
+Levanta un consumer real en un thread:
+
+```ruby
+with_running_worker(
+  queue: unique('test_q'),
+  exchange: unique('test_ex'),
+  exchange_type: 'topic',
+  routing_key: 'users.#'
+) do
+  response = client.request('users/1', method: :get)
+  expect(response['status']).to eq(200)
+end
+# Worker se detiene automáticamente al salir del bloque
+```
+
+### with_spy_worker
+
+Captura mensajes sin procesarlos:
+
+```ruby
+with_spy_worker(queue:, exchange:) do |messages|
+  client.publish('events', body: { type: 'test' })
+  msg = wait_for_message(messages, 5)
+  expect(msg[:body]).to include('type' => 'test')
+end
+```
+
+### unique(name)
+
+Genera nombres únicos para evitar colisiones entre tests:
+
+```ruby
+unique('my_queue')  # → "my_queue_a3f1b2c4"
+# Usa SecureRandom.hex(4)
+```
+
+## Thread Safety Testing
+
+Patrón con `Concurrent::CyclicBarrier`:
+
+```ruby
+barrier = Concurrent::CyclicBarrier.new(10)
+counter = Concurrent::AtomicFixnum.new(0)
+
+threads = 10.times.map do
+  Thread.new do
+    barrier.wait   # Sincroniza inicio
+    session.channel
+    counter.increment
+  end
+end
+
+threads.each(&:join)
+expect(counter.value).to eq(10)
+```
+
+## Skip de Integration Tests
+
+Los tests `:integration` se skipean automáticamente si RabbitMQ no está disponible:
+
+```ruby
+# spec_helper.rb
+config.before(:each, :integration) do
+  skip 'RabbitMQ not available' unless rabbitmq_available?
+end
+```
+
+## Configuración de Test
+
+```ruby
+BugBunny.configure do |config|
+  config.host     = ENV.fetch('RABBITMQ_HOST', 'localhost')
+  config.username = ENV.fetch('RABBITMQ_USER', 'guest')
+  config.password = ENV.fetch('RABBITMQ_PASS', 'guest')
+end
+
+TEST_POOL = ConnectionPool.new(size: 5) { BugBunny.create_connection }
+```
+
+## Ejecutar Tests
+
+```bash
+bundle exec rspec                           # Todos
+bundle exec rspec spec/unit/                # Solo unit
+bundle exec rspec spec/integration/         # Solo integration (requiere RabbitMQ)
+bundle exec rspec spec/unit/session_spec.rb # Archivo específico
+```

data/skills.lock

@@ -0,0 +1,24 @@
+---
+synced_at: '2026-04-04 12:24:37'
+skills:
+- name: documentation-writer
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/documentation-writer"
+- name: gem-release
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/gem-release"
+- name: quality-code
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/quality-code"
+- name: rabbitmq-expert
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/rabbitmq-expert"
+- name: skill-builder
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/skill-builder"
+- name: skill-manager
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/skill-manager"
+- name: yard
+  scope: local
+  path: "/Users/gabriel/src/gems/bug_bunny/.agents/skills/yard"

data/skills.yml

@@ -0,0 +1,19 @@
+mcps:
+  - github
+skills:
+  - name: skill-manager
+    repo: sequre/ai_knowledge
+  - name: yard
+    repo: sequre/ai_knowledge
+  - name: quality-code
+    repo: sequre/ai_knowledge
+  - name: gem-release
+    repo: sequre/ai_knowledge
+  - name: skill-builder
+    repo: sequre/ai_knowledge
+  - name: rabbitmq-expert
+    repo: martinholovsky/claude-skills-generator
+    path: skills/rabbitmq-expert
+  - name: documentation-writer
+    repo: github/awesome-copilot
+    path: skills/documentation-writer

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bug_bunny
 version: !ruby/object:Gem::Version
-  version: 4.8.0
+  version: 4.8.1
 platform: ruby
 authors:
 - gabix
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-04-02 00:00:00.000000000 Z
+date: 2026-04-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bunny
@@ -229,36 +229,22 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".agents/skills/documentation-writer/SKILL.md"
+- ".agents/skills/gem-release/SKILL.md"
+- ".agents/skills/quality-code/SKILL.md"
 - ".agents/skills/rabbitmq-expert/SKILL.md"
-- ".claude/commands/gem-ai-setup.md"
-- ".claude/commands/pr.md"
-- ".claude/commands/release.md"
-- ".claude/commands/rubocop.md"
-- ".claude/commands/service-ai-setup.md"
-- ".claude/commands/test.md"
-- ".claude/commands/yard.md"
+- ".agents/skills/sentry/SKILL.md"
+- ".agents/skills/sentry/references/api-endpoints.md"
+- ".agents/skills/sentry/scripts/sentry.rb"
+- ".agents/skills/skill-builder/SKILL.md"
+- ".agents/skills/skill-manager/SKILL.md"
+- ".agents/skills/skill-manager/scripts/sync.rb"
+- ".agents/skills/yard/SKILL.md"
+- ".agents/skills/yard/references/tipos.md"
 - CHANGELOG.md
 - CLAUDE.md
 - README.md
 - Rakefile
-- docs/_index.md
-- docs/ai/_index.md
-- docs/ai/antipatterns.md
-- docs/ai/api.md
-- docs/ai/architecture.md
-- docs/ai/errors.md
-- docs/ai/faq_external.md
-- docs/ai/faq_internal.md
-- docs/ai/glossary.md
-- docs/concepts.md
-- docs/howto/controller.md
-- docs/howto/middleware_client.md
-- docs/howto/middleware_consumer.md
-- docs/howto/rails.md
-- docs/howto/resource.md
-- docs/howto/routing.md
-- docs/howto/testing.md
-- docs/howto/tracing.md
 - initializer_example.rb
 - lib/bug_bunny.rb
 - lib/bug_bunny/client.rb
@@ -284,7 +270,17 @@ files:
 - lib/generators/bug_bunny/install/templates/initializer.rb
 - lib/tasks/bug_bunny.rake
 - plan_test.txt
+- skill/SKILL.md
+- skill/references/client-middleware.md
+- skill/references/consumer.md
+- skill/references/controller.md
+- skill/references/errores.md
+- skill/references/resource.md
+- skill/references/routing.md
+- skill/references/testing.md
 - skills-lock.json
+- skills.lock
+- skills.yml
 - spec/integration/client_spec.rb
 - spec/integration/consumer_middleware_spec.rb
 - spec/integration/controller_spec.rb
@@ -312,7 +308,7 @@ metadata:
   homepage_uri: https://github.com/gedera/bug_bunny
   source_code_uri: https://github.com/gedera/bug_bunny
   changelog_uri: https://github.com/gedera/bug_bunny/blob/main/CHANGELOG.md
-  documentation_uri: https://github.com/gedera/bug_bunny/blob/v4.8.0/docs
+  documentation_uri: https://github.com/gedera/bug_bunny/blob/v4.8.1/skill
 post_install_message:
 rdoc_options: []
 require_paths:

data/.claude/commands/gem-ai-setup.md

@@ -1,174 +0,0 @@
-Generate or update the complete AI documentation suite for this gem.
-
-This skill is invoked automatically by `/release`. It can also be run standalone to update docs without a full release.
-
-BugBunny's `docs/ai/` is the **golden example** of the expected output quality. When in doubt, read it.
-
----
-
-## Step 1 — Discover the current state
-
-Read in order:
-1. `lib/bug_bunny/version.rb` (or equivalent) — current version
-2. `docs/_index.md` — if it exists, it lists all files to update and their purpose
-3. `docs/ai/_index.md` — if it exists, it has the current profile (minimal/full) and file list
-4. `gemspec` — gem name, summary, description, dependencies
-5. `CLAUDE.md` — architecture, components, patterns, extension hooks
-
-If `docs/ai/` does not exist yet, this is a **first-time generation**. Create from scratch.
-If it exists, **update only the sections affected by the changes in this release**.
-
----
-
-## Step 2 — Determine the profile
-
-**Full profile** when any of these apply:
-- Gem is public (has a homepage or published to RubyGems)
-- Gem has multiple audiences (internal maintainers + external integrators)
-- Gem has a non-trivial public API (multiple classes, errors, configuration)
-
-**Minimal profile** when all of these apply:
-- Gem is internal-only
-- Single audience
-- Simple API (one entry point, few methods)
-
-Full profile files: `_index.md`, `glossary.md`, `architecture.md`, `api.md`, `faq_internal.md`, `faq_external.md`, `antipatterns.md`, `errors.md`
-Minimal profile files: `_index.md`, `api.md`, `errors.md`
-
----
-
-## Step 3 — Analyze the codebase
-
-Read the following to generate accurate content:
-- All files under `lib/` — public API, class responsibilities, method signatures
-- `spec/` or `test/` — usage patterns, edge cases, what errors are expected
-- `CHANGELOG.md` — what changed in this version (for updating existing docs)
-- `docs/howto/` — existing human docs to stay consistent with
-
----
-
-## Step 4 — Generate or update each file
-
-Apply these rules to every file:
-
-**RAG optimization rules (mandatory):**
-1. Each section ≤ 400 tokens — chunks must be self-contained
-2. Each section self-contained — do not assume context from previous sections
-3. `faq_*.md` always in strict Q&A format — H3 with the question, answer ≤ 150 words
-4. `glossary.md` one entry per term — term in bold, definition in 1-3 lines
-5. `errors.md` one entry per error — name, cause, how to reproduce, how to resolve
-6. No introductory prose — go straight to content
-
-### `_index.md`
-
-Frontmatter manifest. Update `version:` to the new version. Keep `profile:`, `kind:`, `audiences:` stable unless the gem changed fundamentally. List every file under `files:` with its audience.
-
-Reference: `docs/ai/_index.md` in BugBunny.
-
-### `glossary.md`
-
-Domain terms specific to this gem. Include:
-- Core abstractions introduced by the gem
-- Terms a developer needs to understand to use the gem correctly
-- Terms that have a non-obvious meaning in this context
-
-Do NOT include generic Ruby or framework terms unless the gem redefines them.
-
-Reference: `docs/ai/glossary.md` in BugBunny.
-
-### `architecture.md`
-
-Internal-facing. Include:
-- Component map (ASCII diagram if useful)
-- How the components interact at runtime
-- Key design decisions and why (not just what)
-- Thread safety considerations if relevant
-- Caching or lifecycle patterns
-
-Reference: `docs/ai/architecture.md` in BugBunny.
-
-### `api.md`
-
-External-facing. Include:
-- Configuration block with all options, types, defaults, and constraints
-- Every public class with its public methods: signature, parameters, return type, description
-- Code examples for each major operation
-- Class-level configuration options (`.with`, class attributes, etc.)
-
-Reference: `docs/ai/api.md` in BugBunny.
-
-### `faq_internal.md`
-
-Q&A for the gem maintainer. Cover:
-- Non-obvious implementation decisions ("why X instead of Y?")
-- Thread safety and concurrency considerations
-- How to extend or hook into the gem
-- Common mistakes when modifying the gem internals
-
-Each Q&A: H3 for the question, answer ≤ 150 words, no preamble.
-
-Reference: `docs/ai/faq_internal.md` in BugBunny.
-
-### `faq_external.md`
-
-Q&A for the developer integrating the gem. Cover:
-- Setup and configuration questions
-- How to perform the most common operations
-- Error handling patterns
-- Testing patterns
-- Performance and tuning questions
-
-Each Q&A: H3 for the question, answer ≤ 150 words, no preamble.
-
-Reference: `docs/ai/faq_external.md` in BugBunny.
-
-### `antipatterns.md`
-
-What NOT to do. For each antipattern:
-1. Name it clearly
-2. Show the wrong code
-3. Explain why it's wrong (not just "it's bad")
-4. Show the correct alternative
-
-Reference: `docs/ai/antipatterns.md` in BugBunny.
-
-### `errors.md`
-
-All exceptions the gem raises. For each:
-- Class name and inheritance
-- Cause (what triggers it)
-- How to reproduce it (minimal example)
-- How to resolve it
-
-Reference: `docs/ai/errors.md` in BugBunny.
-
----
-
-## Step 5 — Update docs/howto/ and docs/concepts.md
-
-Read `docs/_index.md` (human documentation section) to know which files exist.
-Update only the sections affected by the changes in this release.
-Do not rewrite files that were not affected by the changes.
-
----
-
-## Step 6 — Update README.md
-
-Generate or update README.md after `docs/howto/` is already updated.
-README structure:
-1. One-line description
-2. Installation (`gem 'gem_name'` in Gemfile)
-3. Quick start — two minimal code examples (publisher side + consumer/server side if applicable)
-4. Features list for the current version
-5. Links to `docs/` for deeper guides
-
-Keep it under 150 lines. README is the entry point — `docs/` is the depth.
-
----
-
-## Step 7 — Show diff and wait for approval
-
-Show the complete diff of all generated/updated files.
-Wait for developer approval before proceeding.
-The developer may adjust content before confirming.
-Do NOT proceed to version bump or CHANGELOG until approved.

data/.claude/commands/pr.md

@@ -1,53 +0,0 @@
-Create a Pull Request for BugBunny via GitHub CLI. Usage: /pr
-
-Creá un PR desde la rama actual hacia `main` usando `gh`.
-
-## Pasos
-
-1. **Correr tests** — si fallan, detener todo:
-   ```bash
-   source /opt/homebrew/opt/chruby/share/chruby/chruby.sh && chruby ruby-3.3.8
-   bundle exec rspec
-   ```
-2. **autocorregir rubocop** - si fallan, detener todo
-   ```bash
-   bundle exec rubocop -a
-   ```
-3. **Ejecutar `/gem-ai-setup`** — genera/actualiza `docs/howto/`, `docs/ai/` y `README.md`.
-   Esperar aprobación del developer antes de continuar.
-4. Verificá que hay commits en la rama que no están en main: `git log main..HEAD --oneline`
-5. Revisá todos los cambios del PR: `git diff main...HEAD`
-6. Determiná el tipo de cambio (feature, bugfix, refactor, docs, chore)
-7. Creá el PR con `gh pr create`:
-
-```bash
-gh pr create --title "tipo: descripción breve" --body "$(cat <<'EOF'
-## Summary
-- Bullet points de los cambios principales
-
-## Test plan
-- [ ] Tests existentes pasan (`/test`)
-- [ ] RuboCop sin offenses (`/rubocop`)
-- [ ] YARD documentado en métodos nuevos/modificados
-
-## Notes
-Contexto adicional si es necesario.
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-EOF
-)"
-```
-
-## Convenciones de título
-
-- `feat: descripción` — feature nueva
-- `fix: descripción` — bugfix
-- `chore: descripción` — mantenimiento, deps, config
-- `docs: descripción` — solo documentación
-- `refactor: descripción` — refactor sin cambio de comportamiento
-
-## Importante
-
-- El remote SSH está roto — si el PR requiere push previo, usar HTTPS temporalmente
-- Mostrar la URL del PR creado al usuario
-- No crear el PR sin confirmación del usuario

data/.claude/commands/release.md

@@ -1,52 +0,0 @@
-Release BugBunny gem. Usage: /release [patch|minor|major]
-
-Ejecutá el flujo completo de release para BugBunny. El argumento determina el tipo de bump:
-- `patch` → bugfix (4.6.1 → 4.6.2)
-- `minor` → feature nueva (4.6.1 → 4.7.0)
-- `major` → breaking change (4.6.1 → 5.0.0)
-
-## Pasos
-
-1. **Leer versión actual** de `lib/bug_bunny/version.rb`
-2. **Calcular nueva versión** según el tipo de bump
-3. **Correr tests** — si fallan, detener todo:
-   ```bash
-   source /opt/homebrew/opt/chruby/share/chruby/chruby.sh && chruby ruby-3.3.8
-   bundle exec rspec
-   ```
-4. **autocorregir rubocop** - si fallan, detener todo
-   ```bash
-   bundle exec rubocop -a
-   ```
-5. **Ejecutar `/gem-ai-setup`** — genera/actualiza `docs/howto/`, `docs/ai/` y `README.md`.
-   Esperar aprobación del developer antes de continuar.
-6. **Actualizar `lib/bug_bunny/version.rb`** con la nueva versión
-7. **Agregar entrada al tope de `CHANGELOG.md`** con formato:
-   ```
-   ## [X.Y.Z] - YYYY-MM-DD
-   ### ✨ New Features / 🐛 Bug Fixes / 💥 Breaking Changes
-   * Descripción de los cambios
-   ```
-8. **Mostrar el diff completo** al usuario y pedir confirmación antes de continuar
-9. **Commit** con mensaje: `feat|fix|chore: descripción breve vX.Y.Z`
-10. **Merge a main** desde `/Users/gabriel/src/gems/bug_bunny`: `git merge --ff-only <branch>`
-11. **Push via HTTPS**:
-    ```bash
-    git remote set-url origin https://github.com/gedera/bug_bunny.git
-    git push origin main
-    git remote set-url origin git@github.com:gedera/bug_bunny.git
-    ```
-12. **Tag y push**:
-    ```bash
-    git tag vX.Y.Z
-    git remote set-url origin https://github.com/gedera/bug_bunny.git
-    git push origin vX.Y.Z
-    git remote set-url origin git@github.com:gedera/bug_bunny.git
-    ```
-
-## Importante
-
-- Nunca commitear ni pushear sin confirmación explícita del usuario
-- El worktree de main está en `/Users/gabriel/src/gems/bug_bunny`
-- SSH está roto — siempre usar HTTPS para push y restaurar SSH después
-- Sourcear chruby antes de cualquier comando Ruby: `source /opt/homebrew/opt/chruby/share/chruby/chruby.sh && chruby ruby-3.3.8`

data/.claude/commands/rubocop.md

@@ -1,22 +0,0 @@
-Run RuboCop for BugBunny. Usage: /rubocop [--fix]
-
-Ejecutá RuboCop con rubocop-rails-omakase sobre el código modificado.
-
-## Comandos
-
-Sin argumentos — solo reporte:
-```bash
-source /opt/homebrew/opt/chruby/share/chruby/chruby.sh && chruby ruby-3.3.8 && bundle exec rubocop
-```
-
-Con `--fix` — autocorrect seguro:
-```bash
-source /opt/homebrew/opt/chruby/share/chruby/chruby.sh && chruby ruby-3.3.8 && bundle exec rubocop -a
-```
-
-## Reglas importantes
-
-- **Solo corregir código nuevo o modificado en el PR actual** — nunca tocar código existente no relacionado
-- Si hay offenses que requieren intervención manual (no autocorregibles), reportalos con línea y descripción
-- rubocop-rails-omakase tiene opiniones fuertes sobre estilo — seguirlas sin discutir
-- Si hay un offense legítimo que debe ignorarse, usar `# rubocop:disable Cop/Name` en la línea específica con un comentario explicativo