x_aeon_agents 2.5.3 → 2.6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e2c9a713fb342108acdefa7029af3e0d84d7f6d225f611873832a55e7e8f7b31
-  data.tar.gz: 8c41d19d08532755b31176f5621bbd1ba54e4bbc348a4b42a91bc7cd8e4fa0b0
+  metadata.gz: 9e35c93ce34d5bcbd4425bd104b6f7e318a5d80d32176d9c4292d886acf25ae5
+  data.tar.gz: 425cc6c7babc621315dddba419cf3a0e331104d902b4794ea7bab3ea979231fe
 SHA512:
-  metadata.gz: 65bb91d2ffac6d193cfc0cca6082e550c15a869c0bb47c3672b2b14b68f57bbd9f45b04d333b2340eec1a0c8497d70a3e89650f69ea2e5d5c9964fd704057bb1
-  data.tar.gz: 42ba29ec31bd04a7b55b3193e8d62f2f42daa15bda651d832bfd7a637577688ffdf4fc56efabfec06a7695b7f4d52404075383af33d6c2f06fbe3764b9a30acf
+  metadata.gz: a0eca635a5b4a026f14c88d1bc041fe24d78355fa06c2a0dd00644df0a7c2d6265a7c20ecfed8ffd16c8075e4e9a84e9486b3a2e1dcb9abf0e0ddc8eee57c40d
+  data.tar.gz: c886025ea23528c114403da962f878cf8d2176a778c81211fdac2fe98881c44ea29310c588c3ec758199b1cbc9357822cefc2beb769c538cf4e1c601eaa419fb

data/CHANGELOG.md

@@ -1,3 +1,21 @@
+# [v2.6.1](https://github.com/Muriel-Salvan/x_aeon_agents/compare/v2.6.0...v2.6.1) (2026-11-07 01:29:31)
+
+### Patches
+
+* [refactor(agents): improve prompts to avoid artifact files](https://github.com/Muriel-Salvan/x_aeon_agents/commit/71afa833c80e574eb74b6349e6371762a447350a)
+
+# [v2.6.0](https://github.com/Muriel-Salvan/x_aeon_agents/compare/v2.5.3...v2.6.0) (2026-11-06 19:39:17)
+
+## Global changes
+### Patches
+
+* [feat(agents): scope repository file access in agent prompts](https://github.com/Muriel-Salvan/x_aeon_agents/commit/703f1a0b672018fd11f8ae266054c330d887e4e7)
+
+## Changes for agents
+### Features
+
+* [feat(agents): scope repository file access in agent prompts](https://github.com/Muriel-Salvan/x_aeon_agents/commit/703f1a0b672018fd11f8ae266054c330d887e4e7)
+
 # [v2.5.3](https://github.com/Muriel-Salvan/x_aeon_agents/compare/v2.5.2...v2.5.3) (2026-11-06 18:10:39)
 
 ### Patches

data/TODO.md

@@ -1,12 +1,3 @@
-* Add the repository to be worked on in the prompts, and with the constraint that it should not edit files outside of this repo:
-  - - "Your git repository root is the current working directory. Use __relative__ paths only, and always prefix commands with `git rev-parse --show-toplevel` verification; never use `/workspace` absolute paths (that is a *different* checkout of the base branch)."
-* Improve prompts:
-  - "Never create files (`ARTIFACT_*`, `/tmp/*`) to hold artifacts. Put the fenced ` ```json output_artifact=… ` block in your final message and end the turn with __no tool call__. If `ARTIFACT_PLAN_MODIFICATIONS` has nothing to report, say so in plain text."
-* Improve Tester prompt:
-  - "Fix __all__ issues reported in `ARTIFACT_TESTS_OUTPUT` in this iteration (not a subset)."
-  - "Identify the exact failing spec file(s) and run __those__ (`<tests_cmd> spec/scenarios/code_quality_spec.rb`), then a final full run. __Never__ conclude success from a partial run."
-  - "Quote the final summary line of your verification run in your answer."
-* Replace `JSON.dump(artifact_content)` by `JSON.pretty_generate(artifact_content)` (and `JSON.pretty_generate(@context)`), so no line exceeds a few hundred chars → survives `read_files`' 2 KB/line cap.
 * Make the tester loop with a max retries when the same tests are failing (maybe use a JSON/XML output format for tests that allow for parsing which test fail and only give this information in the prompt).
 * Don't use project skills and rules: it adds noise to the LLMs that scan the files and code base. Use only global objects from dedicated config dirs.
 * Add desktop notification when user input is needed.

data/lib/x_aeon_agents/agents/coder_agent.rb

@@ -24,6 +24,8 @@ module XAeonAgents
             Given the user's prompt, you should use the tools available to you to answer user's question.
           EO_OBJECTIVE
           system_instructions: <<~EO_INSTRUCTIONS,
+            #{Helpers.repository_access_system_instructions}
+
             Always gather all the necessary context before starting to work on a task.
             For example, if you are generating a unit test or new code, make sure you understand the requirement, the naming conventions, frameworks and libraries used and aligned in the current codebase, and the environment and commands used to run and test the code etc.
             Always validate the new unit test at the end including running the code if possible for live feedback.
@@ -59,6 +61,7 @@ module XAeonAgents
               emit independent read_files, search_codebase, and run_commands calls together in one response;
               emit multiple editor calls together when editing different files or non-overlapping regions.
             - Always verify the files you have edited or created at the end of the task to ensure they are completed and working as expected.
+            - #{Helpers.repository_access_constraint(writable: true)}
 
             REMEMBER, be helpful and proactive!
             Don't ask for permission to do something when you can do it!

data/lib/x_aeon_agents/agents/documenter_agent.rb

@@ -22,6 +22,22 @@ module XAeonAgents
         super(
           name: 'Documenter',
           objective: 'Ensure documentation reflects the current product behavior and usage after a new development.',
+          system_instructions: <<~EO_INSTRUCTIONS,
+            #{Helpers.repository_access_system_instructions}
+
+            Always gather all the necessary context before starting to work on a task.
+            For example, make sure you understand the current behavior of the product by exploring the code, the tests, the existing documentation and the configuration files, so that the documentation you write reflects the current state of the project.
+            Begin by analyzing the user's input and gathering any necessary additional context.
+            Then, present your plan at the start of your response along with tool calls before proceeding with the task.
+            It's OK for this section to be quite long.
+
+            Review each question carefully and answer it with detailed, accurate information.
+
+            If you need more information, use one of the available tools or ask for clarification instead of making assumptions or lies.
+
+            When you have completed the task, please provide a summary of what you did and any relevant information that the user should know.
+            This will help ensure that the user understands the changes made and can easily follow up if they have any questions or need further assistance.
+          EO_INSTRUCTIONS
           constraints: <<~EO_CONSTRAINTS,
             - Only update documentation files.
             - Do NOT change any code or test.
@@ -29,6 +45,7 @@ module XAeonAgents
             - NEVER explain that something was removed, renamed, or fixed.
             - Documentation describes the CURRENT STATE only.
             - Documentation is NOT a changelog.
+            - #{Helpers.repository_access_constraint(writable: true)}
           EO_CONSTRAINTS
           **agent_params
         )

data/lib/x_aeon_agents/agents/feedback_analyst_agent.rb

@@ -43,11 +43,21 @@ module XAeonAgents
           name: 'Feedback analyst',
           role: 'You are a feedback analyst agent, analyzing feedback from a Pull Request and devising new requirements to address this feedback.',
           objective: 'Extract requirements from Pull Request comments',
+          system_instructions: <<~EO_INSTRUCTIONS,
+            #{Helpers.repository_access_system_instructions}
+
+            Always gather all the necessary context before starting to work on a task: read the Pull Request description, files diffs and conversations, and explore the repository's code when needed.
+            Begin by analyzing the user's input and gathering any necessary additional context.
+            Review each question carefully and answer it with detailed, accurate information.
+            If you need more information, use one of the available tools or ask for clarification instead of making assumptions or lies.
+            Do not indicate that you will perform an action without actually doing it.
+          EO_INSTRUCTIONS
           constraints: <<~EO_CONSTRAINTS,
             - You are in read-only mode.
             - Do NOT modify or write any file.
             - Focus only on agent-directed comments (/agent) for requirement extraction.
             - Output clear, actionable requirements or "No requirements" if none exist.
+            - #{Helpers.repository_access_constraint}
           EO_CONSTRAINTS
           **agent_params
         )

data/lib/x_aeon_agents/agents/plan_generator_agent.rb

@@ -32,11 +32,22 @@ module XAeonAgents
           name: 'Plan generator',
           role: 'You are an implementation plan generator agent',
           objective: 'Produce a full and detailed implementation plan that can be used to implement some requirements.',
+          system_instructions: <<~EO_INSTRUCTIONS,
+            #{Helpers.repository_access_system_instructions}
+
+            Always gather all the necessary context before starting to work on a task: read the relevant code, tests, documentation and configuration files of the repository.
+            Begin by analyzing the user's input and gathering any necessary additional context.
+            Review each question carefully and answer it with detailed, accurate information.
+            If you need more information, use one of the available tools or ask for clarification instead of making assumptions or lies.
+            Do not indicate that you will perform an action without actually doing it.
+          EO_INSTRUCTIONS
           constraints: <<~EO_CONSTRAINTS,
             - You are in read-only mode.
             - Do NOT modify or write any file.
             - You may only analyze and propose plans.
             - Do NOT execute the plan yourself.
+            - #{Helpers.repository_access_constraint}
+            - Never create files (`ARTIFACT_*`, `/tmp/*`) to hold artifacts. Put the fenced ` ```json output_artifact=… ` block in your final message and end the turn with __no tool call__.
           EO_CONSTRAINTS
           **agent_params
         )

data/lib/x_aeon_agents/agents/readme/about_analyzer_agent.rb

@@ -39,12 +39,20 @@ module XAeonAgents
               - The 1-line description of the project, using Markdown.
               - A high-level overview (about section) of the project in Markdown format, compatible with Github flavor.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifacts content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact contents: only provide the content as required.
               - Only focus on the specific scope of the required documentation required.
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/contributing_agent.rb

@@ -29,6 +29,13 @@ module XAeonAgents
               Focus on giving community specific guidelines (issues, pull requests, CI, fork...).
               Use emphasis, bullet points, useful links to the project resources and small emojis to better format your section.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
@@ -37,6 +44,7 @@ module XAeonAgents
                 Do not try to document other parts.
               - Do not describe the technical setup or prequisites, as they are already covered by other sections.
               - Do not cover how to develop in this project: it is already covered in other sections.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/development_agent.rb

@@ -36,6 +36,13 @@ module XAeonAgents
               - package the project deliverables,
               - perform common development tasks.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
@@ -44,6 +51,7 @@ module XAeonAgents
                 Do not try to document other parts.
               - Do not cover the end-user main requirements and prerequisites: they are already covered in other sections.
               - Do not cover the contribution workflow (pull requests, CI, issues...): this is already covered in other sections.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/documentation_agent.rb

@@ -27,12 +27,20 @@ module XAeonAgents
               Explore the project's documentation files and resources to identify all available documentation.
               Generate a "Documentation" section in Markdown format, compatible with Github flavor, providing links to documentation resources.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
               - Only focus on the specific scope of the required documentation required.
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/features_agent.rb

@@ -29,12 +29,20 @@ module XAeonAgents
               Use emphasis, bullet points and small emojis to illustrate in a readable way the list of features.
               Don't provide an overall description of the project: another section is already doing it.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
               - Only focus on the specific scope of the required documentation required.
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/how_it_works_agent.rb

@@ -30,6 +30,13 @@ module XAeonAgents
               You can use SocratiCode if it is available to get a better understanding of this project.
               You can use Mermaid graphs to also illustrate the way this project works.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
@@ -37,6 +44,7 @@ module XAeonAgents
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
               - Do not provide long paragraphs: focus on readability by splitting long paragraphs into several short ones.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/license_agent.rb

@@ -27,12 +27,20 @@ module XAeonAgents
               Analyze the project's LICENSE file to identify the license type and terms.
               Generate a "License" section in Markdown format, compatible with Github flavor, describing the project license.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
               - Only focus on the specific scope of the required documentation required.
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/public_api_agent.rb

@@ -27,6 +27,13 @@ module XAeonAgents
               Analyze the project's codebase to identify all public APIs, classes, methods, and interfaces exposed to users.
               Generate a "Public API" section in Markdown format, compatible with Github flavor, documenting the public API surface.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
@@ -34,6 +41,7 @@ module XAeonAgents
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
               - Only document public API entry points: executables and library public methods belonging to yarn `Public API` group.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/quick_start_agent.rb

@@ -33,6 +33,13 @@ module XAeonAgents
               - If this project defines a web app, explain how to install this web app, run it and access it using a web browser.
               This section should be concise: don't cover all features, just simple install and startup guides for the main happy paths.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
@@ -40,6 +47,7 @@ module XAeonAgents
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
               - This section is not meant for developers: don't describe how to develop, test, document, package or contribute to this project.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/readme/requirements_agent.rb

@@ -27,12 +27,20 @@ module XAeonAgents
               Analyze the project's dependencies, runtime environment, and prerequisites.
               Generate a "Requirements" section in Markdown format, compatible with Github flavor, listing all prerequisites needed to use or run the project.
             EO_OBJECTIVE
+            system_instructions: <<~EO_INSTRUCTIONS,
+              #{Helpers.repository_access_system_instructions}
+
+              Always gather all the necessary context before starting to work on a task: explore the current repository's code, configuration and documentation to ground your analysis in the actual project.
+              If you need more information, use one of the available tools instead of making assumptions.
+              Do not indicate that you will perform an action without actually doing it.
+            EO_INSTRUCTIONS
             constraints: <<~EO_CONSTRAINTS,
               - The required output artifact content should only contain the required content, without additional header or title.
               - Do not explain or describe the artifact content: only provide the content as required.
               - Only focus on the specific scope of the required documentation required.
                 Other agents will generate other sections of the README.
                 Do not try to document other parts.
+              - #{Helpers.repository_access_constraint}
             EO_CONSTRAINTS
             **agent_params
           )

data/lib/x_aeon_agents/agents/tester_agent.rb

@@ -42,8 +42,33 @@ module XAeonAgents
             Fix any regression that has been induced by new features or fixes, while keeping the initial requirements and implementation plan in mind.
             If the decisions taken in the implementation plan prevent you from fixing regressions, modify the implementation plan and report those modifications to the user.
           EO_OBJECTIVE
+          constraints: <<~EO_CONSTRAINTS,
+            - #{Helpers.repository_access_constraint(writable: true)}
+            - Never create files (`ARTIFACT_*`, `/tmp/*`) to hold artifacts. Put the fenced ` ```json output_artifact=… ` block in your final message and end the turn with __no tool call__.
+          EO_CONSTRAINTS
           **agent_params
         )
+        self.system_instructions = <<~EO_INSTRUCTIONS
+          #{Helpers.repository_access_system_instructions}
+
+          Always gather all the necessary context before starting to work on a task.
+          For example, make sure you understand the regressions to fix, the naming conventions, frameworks and libraries used and aligned in the current codebase, and the environment and commands used to run and test the code etc.
+          Always run the whole tests suite using the tests command provided, and validate your fixes with live feedback until all tests pass.
+          Begin by analyzing the user's input and gathering any necessary additional context.
+          Then, present your plan at the start of your response along with tool calls before proceeding with the task.
+          It's OK for this section to be quite long.
+
+          Review each question carefully and answer it with detailed, accurate information.
+
+          If you need more information, use one of the available tools or ask for clarification instead of making assumptions or lies.
+
+          Fix __all__ issues reported in the `#{artifact_ref(:tests_output)}` artifact in this iteration (not a subset).
+          Identify the exact failing spec file(s) and run __those__, then a final full run. __Never__ conclude success from a partial run.
+          Quote the final summary line of your verification run in your answer.
+
+          When you have completed the task, please provide a summary of what you did and any relevant information that the user should know, including the final summary line of the tests suite.
+          This will help ensure that the user understands the changes made and can easily follow up if they have any questions or need further assistance.
+        EO_INSTRUCTIONS
       end
     end
   end

data/lib/x_aeon_agents/helpers.rb

@@ -149,6 +149,25 @@ module XAeonAgents
         end
       end
 
+      # Get the system instructions telling agents in which repository they are working.
+      # This instruction is format-agnostic: it does not include any formatting (bullet, header...) so that it can be
+      # included in any system instructions section.
+      #
+      # @return [String] The system instructions about the current repository
+      def repository_access_system_instructions
+        "The current repository in which you are working is `#{Dir.pwd}`."
+      end
+
+      # Get the constraint restricting the files agents are allowed to access.
+      # This constraint is format-agnostic: it does not include any formatting (bullet, header...) so that it can be
+      # included in any constraints section.
+      #
+      # @param writable [Boolean] True if the agent is allowed to write files, false if it is read-only
+      # @return [String] The constraint restricting the agents' file accesses to the current repository
+      def repository_access_constraint(writable: false)
+        "You should only #{writable ? 'read and write' : 'read'} files that are part of the current repository: `#{Dir.pwd}`"
+      end
+
       # Allow user to review and edit content before using it
       #
       # When the interactive mode is disabled (Config.interactive), no review file

data/lib/x_aeon_agents/version.rb

@@ -2,5 +2,5 @@ module XAeonAgents
   # @!group Global API
 
   # Gem version
-  VERSION = '2.5.3'
+  VERSION = '2.6.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: x_aeon_agents
 version: !ruby/object:Gem::Version
-  version: 2.5.3
+  version: 2.6.1
 platform: ruby
 authors:
 - Muriel Salvan