osa_tool 0.2.6__tar.gz → 0.2.7__tar.gz

{osa_tool-0.2.6 → osa_tool-0.2.7}/PKG-INFO

@@ -1,14 +1,13 @@
 Metadata-Version: 2.4
 Name: osa_tool
-Version: 0.2.6
+Version: 0.2.7
 Summary: Tool that just makes your open source project better!
 License-Expression: BSD-3-Clause
 License-File: LICENSE
 Author: ITMO-NSS-team
 Author-email: itmo.nss.team@gmail.com
-Requires-Python: >=3.10,<4.0
+Requires-Python: >=3.11,<4.0
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
@@ -79,8 +78,6 @@ create them from scratch.
 It automates the generation of README, different levels of documentation, CI/CD scripts, etc.
 It also generates advices and recommendations for the repository.
 
-OSA is currently under development, so not all features are implemented.
-
 ---
 
 ## How it works?
@@ -118,7 +115,7 @@ Here is a short video:
    creates a pull request with proposed changes.
 
 4. **Various LLMs**: Use OSA with an LLM accessible via API (e.g., OpenAI, VseGPT, Ollama), a local server, or try
-   an [osa_bot](https://github.com/osa-bot) hosted on ITMO servers.
+   an [osa_bot](https://osa.nsslab.onti.actcognitive.org/) hosted on ITMO servers.
 
 5. **Workflow Generator**: Automatically generates customizable CI/CD workflows for Python repositories,
    including unit tests, code formatting, PEP 8 compliance checks, and PyPI publication.
@@ -178,11 +175,14 @@ docker build --build-arg GIT_USER_NAME="your-user-name" --build-arg GIT_USER_EMA
 
 ### Prerequisites
 
-OSA requires Python 3.10 or higher.
+OSA requires Python 3.11 or higher.
 
-The .env file is required to specify the LLM API key (OPENAI_API_KEY or AUTHORIZATION_KEY) and optionally a Git token. The Git token (GIT_TOKEN) may be omitted if you plan to work with a public repository without creating a fork (using the --no-fork option).
+The .env file is required to specify the LLM API key (OPENAI_API_KEY or AUTHORIZATION_KEY) and optionally a Git token.
+The Git token (GIT_TOKEN) may be omitted if you plan to work with a public repository without creating a fork (using the
+--no-fork option).
 
-Alternatively, instead of GIT_TOKEN, you can use GITHUB_TOKEN, GITLAB_TOKEN, or GITVERSE_TOKEN for GitHub, GitLab, and Gitverse respectively.
+Alternatively, instead of GIT_TOKEN, you can use GITHUB_TOKEN, GITLAB_TOKEN, or GITVERSE_TOKEN for GitHub, GitLab, and
+Gitverse respectively.
 
 When running `osa-tool` from CLI, you need to set the GIT_TOKEN and API key first:
 
@@ -233,23 +233,27 @@ documentation, see the [Workflow Generator README](./osa_tool/workflow/README.md
 
 ### Configuration
 
-| Flag                 | Description                                                                         | Default                     |
-|----------------------|-------------------------------------------------------------------------------------|-----------------------------|
-| `-r`, `--repository` | URL of the GitHub/GitLab/Gitverse repository (**Mandatory**)                        |                             |
-| `-b`, `--branch`     | Branch name of the repository                                                       | Default branch              |
-| `-o`, `--output`     | Path to the output directory                                                        | Current working directory   |
-| `--api`              | LLM API service provider                                                            | `itmo`                      |
-| `--base-url`         | URL of the provider compatible with API OpenAI                                      | `https://api.openai.com/v1` |
-| `--model`            | Specific LLM model to use                                                           | `gpt-3.5-turbo`             |
-| `--top_p`            | Nucleus sampling probability                                                        | `0.95`                      |
-| `--temperature`      | Sampling temperature to use for the LLM output (0 = deterministic, 1 = creative).   | `0.05`                      |
-| `--max_tokens`       | Maximum number of output tokens the model can generate in a single response         | `4096`                      |
-| `--context_window`   | Total number of model context (Input + Output)                                      | `16385`                     |
-| `--attachment`       | Path to a local PDF or .docx file, or a URL to a PDF resource                       | `None`                      |
-| `-m`, `--mode`       | Operation mode for repository processing: `basic`, `auto` (default), or `advanced`. | `auto`                      |
-| `--delete-dir`       | Enable deleting the downloaded repository after processing                          | `disabled`                  |
-| `--no-fork`          | Avoid create fork for target repository                                             | `False`                     |
-| `--no-pull-request`  | Avoid create pull request for target repository                                     | `False`                     |
+| Flag                 | Description                                                                         | Default                        |
+|----------------------|-------------------------------------------------------------------------------------|--------------------------------|
+| `-r`, `--repository` | URL of the GitHub/GitLab/Gitverse repository (**Mandatory**)                        |                                |
+| `-b`, `--branch`     | Branch name of the repository                                                       | Default branch                 |
+| `-o`, `--output`     | Path to the output directory                                                        | Current working directory      |
+| `--api`              | LLM API service provider                                                            | `openai`                       |
+| `--base-url`         | URL of the provider compatible with API OpenAI                                      | `https://openrouter.ai/api/v1` |
+| `--model`            | Specific LLM model to use                                                           | `gpt-3.5-turbo`                |
+| `--top_p`            | Nucleus sampling probability                                                        | `0.95`                         |
+| `--temperature`      | Sampling temperature to use for the LLM output (0 = deterministic, 1 = creative).   | `0.05`                         |
+| `--max_tokens`       | Maximum number of output tokens the model can generate in a single response         | `4096`                         |
+| `--context_window`   | Total number of model context (Input + Output)                                      | `16385`                        |
+| `--attachment`       | Path to a local PDF or .docx file, or a URL to a PDF resource                       | `None`                         |
+| `-m`, `--mode`       | Operation mode for repository processing: `basic`, `auto` (default), or `advanced`. | `auto`                         |
+| `--delete-dir`       | Enable deleting the downloaded repository after processing                          | `disabled`                     |
+| `--no-fork`          | Avoid create fork for target repository                                             | `False`                        |
+| `--no-pull-request`  | Avoid create pull request for target repository                                     | `False`                        |
+
+Also OSA supports custom configuration via TOML files. Use the `--config-file` option to specify a path to custom configuration file. If no custom configuration file is provided, OSA will use the default configuration.
+
+By default, OSA uses a single model for all tasks (specified via `--model`). If you want to use different models for different types of tasks, disable the `--use-single-model` flag and specify models for each task type (`--model-docstring`, `--model-readme`, `--model-validation`, `--model-general`).
 
 To learn how to work with the interactive CLI and view descriptions of all available keys, visit
 the [CLI usage guide](./osa_tool/scheduler/README.md).
@@ -368,9 +372,7 @@ If you use this software, please cite it as below.
     author={Nikitin, Nikolay and Getmanov, Andrey and Popov, Zakhar and 
         Ulyanova Ekaterina and Aksenkin, Yaroslav and 
         Sokolov, Ilya and Boukhanovsky, Alexander},
-    booktitle={Championing Open-source DEvelopment in ML Workshop@ ICML25}
-
-}
+    booktitle={Championing Open-source DEvelopment in ML Workshop@ ICML25}}
 
 ---
 

{osa_tool-0.2.6 → osa_tool-0.2.7}/README.md

@@ -34,8 +34,6 @@ create them from scratch.
 It automates the generation of README, different levels of documentation, CI/CD scripts, etc.
 It also generates advices and recommendations for the repository.
 
-OSA is currently under development, so not all features are implemented.
-
 ---
 
 ## How it works?
@@ -73,7 +71,7 @@ Here is a short video:
    creates a pull request with proposed changes.
 
 4. **Various LLMs**: Use OSA with an LLM accessible via API (e.g., OpenAI, VseGPT, Ollama), a local server, or try
-   an [osa_bot](https://github.com/osa-bot) hosted on ITMO servers.
+   an [osa_bot](https://osa.nsslab.onti.actcognitive.org/) hosted on ITMO servers.
 
 5. **Workflow Generator**: Automatically generates customizable CI/CD workflows for Python repositories,
    including unit tests, code formatting, PEP 8 compliance checks, and PyPI publication.
@@ -133,11 +131,14 @@ docker build --build-arg GIT_USER_NAME="your-user-name" --build-arg GIT_USER_EMA
 
 ### Prerequisites
 
-OSA requires Python 3.10 or higher.
+OSA requires Python 3.11 or higher.
 
-The .env file is required to specify the LLM API key (OPENAI_API_KEY or AUTHORIZATION_KEY) and optionally a Git token. The Git token (GIT_TOKEN) may be omitted if you plan to work with a public repository without creating a fork (using the --no-fork option).
+The .env file is required to specify the LLM API key (OPENAI_API_KEY or AUTHORIZATION_KEY) and optionally a Git token.
+The Git token (GIT_TOKEN) may be omitted if you plan to work with a public repository without creating a fork (using the
+--no-fork option).
 
-Alternatively, instead of GIT_TOKEN, you can use GITHUB_TOKEN, GITLAB_TOKEN, or GITVERSE_TOKEN for GitHub, GitLab, and Gitverse respectively.
+Alternatively, instead of GIT_TOKEN, you can use GITHUB_TOKEN, GITLAB_TOKEN, or GITVERSE_TOKEN for GitHub, GitLab, and
+Gitverse respectively.
 
 When running `osa-tool` from CLI, you need to set the GIT_TOKEN and API key first:
 
@@ -188,23 +189,27 @@ documentation, see the [Workflow Generator README](./osa_tool/workflow/README.md
 
 ### Configuration
 
-| Flag                 | Description                                                                         | Default                     |
-|----------------------|-------------------------------------------------------------------------------------|-----------------------------|
-| `-r`, `--repository` | URL of the GitHub/GitLab/Gitverse repository (**Mandatory**)                        |                             |
-| `-b`, `--branch`     | Branch name of the repository                                                       | Default branch              |
-| `-o`, `--output`     | Path to the output directory                                                        | Current working directory   |
-| `--api`              | LLM API service provider                                                            | `itmo`                      |
-| `--base-url`         | URL of the provider compatible with API OpenAI                                      | `https://api.openai.com/v1` |
-| `--model`            | Specific LLM model to use                                                           | `gpt-3.5-turbo`             |
-| `--top_p`            | Nucleus sampling probability                                                        | `0.95`                      |
-| `--temperature`      | Sampling temperature to use for the LLM output (0 = deterministic, 1 = creative).   | `0.05`                      |
-| `--max_tokens`       | Maximum number of output tokens the model can generate in a single response         | `4096`                      |
-| `--context_window`   | Total number of model context (Input + Output)                                      | `16385`                     |
-| `--attachment`       | Path to a local PDF or .docx file, or a URL to a PDF resource                       | `None`                      |
-| `-m`, `--mode`       | Operation mode for repository processing: `basic`, `auto` (default), or `advanced`. | `auto`                      |
-| `--delete-dir`       | Enable deleting the downloaded repository after processing                          | `disabled`                  |
-| `--no-fork`          | Avoid create fork for target repository                                             | `False`                     |
-| `--no-pull-request`  | Avoid create pull request for target repository                                     | `False`                     |
+| Flag                 | Description                                                                         | Default                        |
+|----------------------|-------------------------------------------------------------------------------------|--------------------------------|
+| `-r`, `--repository` | URL of the GitHub/GitLab/Gitverse repository (**Mandatory**)                        |                                |
+| `-b`, `--branch`     | Branch name of the repository                                                       | Default branch                 |
+| `-o`, `--output`     | Path to the output directory                                                        | Current working directory      |
+| `--api`              | LLM API service provider                                                            | `openai`                       |
+| `--base-url`         | URL of the provider compatible with API OpenAI                                      | `https://openrouter.ai/api/v1` |
+| `--model`            | Specific LLM model to use                                                           | `gpt-3.5-turbo`                |
+| `--top_p`            | Nucleus sampling probability                                                        | `0.95`                         |
+| `--temperature`      | Sampling temperature to use for the LLM output (0 = deterministic, 1 = creative).   | `0.05`                         |
+| `--max_tokens`       | Maximum number of output tokens the model can generate in a single response         | `4096`                         |
+| `--context_window`   | Total number of model context (Input + Output)                                      | `16385`                        |
+| `--attachment`       | Path to a local PDF or .docx file, or a URL to a PDF resource                       | `None`                         |
+| `-m`, `--mode`       | Operation mode for repository processing: `basic`, `auto` (default), or `advanced`. | `auto`                         |
+| `--delete-dir`       | Enable deleting the downloaded repository after processing                          | `disabled`                     |
+| `--no-fork`          | Avoid create fork for target repository                                             | `False`                        |
+| `--no-pull-request`  | Avoid create pull request for target repository                                     | `False`                        |
+
+Also OSA supports custom configuration via TOML files. Use the `--config-file` option to specify a path to custom configuration file. If no custom configuration file is provided, OSA will use the default configuration.
+
+By default, OSA uses a single model for all tasks (specified via `--model`). If you want to use different models for different types of tasks, disable the `--use-single-model` flag and specify models for each task type (`--model-docstring`, `--model-readme`, `--model-validation`, `--model-general`).
 
 To learn how to work with the interactive CLI and view descriptions of all available keys, visit
 the [CLI usage guide](./osa_tool/scheduler/README.md).
@@ -323,8 +328,6 @@ If you use this software, please cite it as below.
     author={Nikitin, Nikolay and Getmanov, Andrey and Popov, Zakhar and 
         Ulyanova Ekaterina and Aksenkin, Yaroslav and 
         Sokolov, Ilya and Boukhanovsky, Alexander},
-    booktitle={Championing Open-source DEvelopment in ML Workshop@ ICML25}
-
-}
+    booktitle={Championing Open-source DEvelopment in ML Workshop@ ICML25}}
 
 ---

osa_tool-0.2.7/osa_tool/config/osa_config.py

@@ -0,0 +1,30 @@
+from pydantic import BaseModel
+
+from osa_tool.config.settings import ConfigManager
+from osa_tool.core.git.git_agent import GitAgent
+from osa_tool.scheduler.workflow_manager import WorkflowManager
+
+
+class OSAConfig(BaseModel):
+    """
+    Global, read-only configuration.
+    Initialized once per session.
+    """
+
+    config_manager: ConfigManager
+    git_agent: GitAgent
+    workflow_manager: WorkflowManager
+
+    # For git_agent
+    create_fork: bool = True
+    create_pull_request: bool = True
+
+    # Clean
+    delete_dir: bool = False
+
+    enable_replanning: bool = True
+    enable_memory: bool = True
+    dry_run: bool = False
+
+    class Config:
+        arbitrary_types_allowed = True

osa_tool-0.2.7/osa_tool/config/prompts/analysis.toml

@@ -0,0 +1,179 @@
+[prompts]
+main_prompt = """
+INPUT DATA:
+
+1. PROJECT NAME: {project_name}
+2. METADATA: {metadata}
+3. REPOSITORY FILE TREE: {repository_tree}
+4. PRESENCE OF IMPORTANT FILES AND DIRECTORIES: {presence_files}
+5. README CONTENT: {readme_content}
+
+TASK:
+
+Generate a JSON report following this exact structure:
+
+{{
+  "structure": {{
+    "compliance": "text",
+    "missing_files": ["list"],
+    "organization": "text"
+  }},
+  "readme": {{
+    "readme_quality": "text"
+    "project_description": "Yes/No/Partial",
+    "installation": "Yes/No/Partial",
+    "usage_examples": "Yes/No/Partial",
+    "contribution_guidelines": "Yes/No/Partial",
+    "license_specified": "Yes/No/Partial",
+    "badges_present": "Yes/No/Partial"
+  }},
+  "documentation": {{
+    "tests_present": "Yes/No/Partial",
+    "docs_quality": "text",
+    "outdated_content": boolean
+  }},
+  "assessment": {{
+    "key_shortcomings": ["list"],
+    "recommendations": ["list"]
+  }}
+}}
+
+RULES:
+
+- Use double quotes for JSON
+- No markdown formatting
+- Only use Yes/No/Partial for readme fields and tests_present
+- Be strictly factual about file presence
+- Check for the presence of the directory with tests
+- Prioritize 3 most critical recommendations
+
+"""
+
+after_report_text_prompt = """
+DEFINITIONS:
+
+translate_dirs — Translate directory names to English
+convert_notebooks — Convert Jupyter notebooks to Python scripts
+translate_readme — Translate README file to English
+ensure_license — Ensure a LICENSE file is present
+community_docs — Add or update community documentation files
+docstring — Add or update docstrings in source code
+report — Generate refactoring report
+readme — Create a README file
+requirements — Add or update requirements file
+organize — Reorganize project structure
+about — Add project description or about section
+validate_paper — Validate academic paper files
+validate_doc — Validate documentation files
+generate_workflows — Generate CI or automation workflows
+include_tests — Add or include tests
+include_black — Add Black code formatter
+include_pep8 — Add PEP8 compliance checks
+include_autopep8 — Add autopep8 formatter
+include_fix_pep8 — Automatically fix PEP8 issues
+include_pypi — Prepare project for PyPI publishing
+python_versions — Specify supported Python versions
+pep8_tool — Configure PEP8 checking tool
+use_poetry — Use Poetry for dependency management
+include_codecov — Add Codecov integration
+
+
+INPUT DATA (tasks list):
+
+{tasks_list}
+
+TASK:
+
+Write a connected textual summary of the repository refactoring.
+
+REQUIREMENTS:
+- Write approximately two short paragraphs
+- Use plain text only
+- Do not use markdown
+- Do not use bullet points or lists
+- Do NOT mention tasks that were not performed
+- Do NOT explain why something was not done
+- Do NOT use modal or speculative language (avoid words like "may", "might", "likely")
+- Describe only actions that were actually performed
+- Use neutral but natural technical language
+- Write in confident past tense
+- Base the text ONLY on tasks with value "Yes"
+
+STYLE:
+- Clear and readable
+- Slightly narrative, but professional
+- No bureaucratic or legalistic phrasing
+- No assumptions or interpretation beyond task definitions
+
+OUTPUT:
+Return only the text summary.
+Do not add any explanations or extra text.
+"""
+
+after_report_blocks_prompt = """
+TASK DEFINITIONS:
+
+translate_dirs — Translate directory names to English
+convert_notebooks — Convert Jupyter notebooks to Python scripts
+translate_readme — Translate README file to English
+ensure_license — Ensure a LICENSE file is present
+community_docs — Add or update community documentation files
+docstring — Add or update docstrings in source code
+report — Generate refactoring report
+readme — Create a README file
+requirements — Add or update requirements file
+organize — Reorganize project structure
+about — Add project description or about section
+validate_paper — Validate academic paper files
+validate_doc — Validate documentation files
+generate_workflows — Generate CI or automation workflows
+include_tests — Add or include tests
+include_black — Add Black code formatter
+include_pep8 — Add PEP8 compliance checks
+include_autopep8 — Add autopep8 formatter
+include_fix_pep8 — Automatically fix PEP8 issues
+include_pypi — Prepare project for PyPI publishing
+python_versions — Specify supported Python versions
+pep8_tool — Configure PEP8 checking tool
+use_poetry — Use Poetry for dependency management
+include_codecov — Add Codecov integration
+
+
+INPUT DATA (tasks list):
+
+{tasks_list}
+
+TASK:
+
+You must summarize the result of repository refactoring based ONLY on the tasks listed above.
+
+Group tasks into logical blocks.
+Each logical block must contain:
+- a short name (plain sentence)
+- a short description (plain sentence)
+- a list of task numbers that belong to this block
+
+OUTPUT FORMAT:
+
+Return ONLY valid JSON.
+No extra text, no explanations, no markdown.
+
+JSON structure:
+[
+  {{
+    "name": "Block name as a plain sentence",
+    "description": "Short description as a plain sentence",
+    "tasks": [1, 2]
+  }}
+]
+
+RULES (IMPORTANT):
+
+1. Use double quotes only
+2. Output must be valid JSON
+3. Use ONLY task numbers from the input list
+4. Every task from 1 to 7 MUST be used exactly once
+5. Do NOT invent new tasks
+7. "tasks" must contain only numbers
+
+"""

osa_tool-0.2.7/osa_tool/config/prompts/osa_agent.toml

@@ -0,0 +1,42 @@
+[prompts]
+intent_router = """
+Analyze the following user request and any attached context:
+
+User Request: {user_request}
+Attachment: {attachment}
+
+Return the result **strictly in the JSON format described above**.
+"""
+
+planner = """
+User request:
+{user_request}
+
+Detected intent: {intent}
+Task scope: {task_scope}
+
+Repository overview:
+{repo_data}
+
+Available operations:
+{available_operations}
+
+Select the operations that best satisfy the user request.
+"""
+
+detect_arguments = """
+User request:
+{user_request}
+
+Operations with additional arguments:
+{operations}
+"""
+
+pr_summarizer = """
+Summarize the following repository changes into a Pull Request description.
+
+Operation events:
+{events}
+
+Write a short summary suitable for a PR body.
+"""

osa_tool-0.2.7/osa_tool/config/prompts/requirements.toml

@@ -0,0 +1,31 @@
+[prompts]
+merge_requirements = """
+You are a Senior Python DevOps engineer.
+Your task is to merge two `requirements.txt` file contents into one final list.
+
+INPUT DATA:
+1. OLD_REQUIREMENTS (contains preferred versions/constraints):
+{old_requirements}
+
+2. NEW_REQUIREMENTS (generated from code analysis, acts as the source of truth for used libraries):
+{new_requirements}
+
+TASK:
+Merge these two lists into a single valid list of strings.
+
+RULES:
+1. The `NEW_REQUIREMENTS` list determines WHICH libraries must be included.
+2. For each library in `NEW_REQUIREMENTS`:
+   - If it exists in `OLD_REQUIREMENTS`, use the version string/constraints from `OLD_REQUIREMENTS`.
+   - If it does NOT exist in `OLD_REQUIREMENTS`, keep the version from `NEW_REQUIREMENTS`.
+3. If a library exists in `OLD_REQUIREMENTS` but NOT in `NEW_REQUIREMENTS`:
+   - REMOVE IT. It is unused.
+4. Output ONLY a valid JSON object with a key "dependencies" containing a list of strings.
+
+Example Output:
+{{
+  "dependencies": ["requests==2.25.1", "pandas>=2.0.0", "numpy"]
+}}
+
+Do not add any explanations, comments or markdown blocks.
+"""

osa_tool-0.2.7/osa_tool/config/prompts/system_messages.toml

@@ -0,0 +1,100 @@
+[prompts]
+# OSA AGENTS
+intent_router = """
+You are an intelligent assistant called IntentRouter.
+Your task is to classify user requests into intents and determine the scope of the task in a software repository.
+Always respond **strictly in JSON** matching this structure:
+
+{{
+  "intent": "new_task | feedback | unknown",
+  "task_scope": "none | analysis | docs | codebase | full_repo",
+  "confidence": "<float value between 0 and 1>"
+}}
+
+INTENT definitions:
+- new_task: A brand-new task requiring some action or output.
+- feedback: Comments, corrections, or minor updates to existing outputs.
+- unknown: Cannot confidently determine the intent.
+
+TASK_SCOPE definitions:
+- none: No actionable task, purely informational request.
+- analysis: Only analysis or reporting, without modifying code or docs.
+- docs: Focus on modifying documentation, README, or textual content in the repository.
+- codebase: Focus on modifying source code, structure, and project files (for examples requirements).
+- full_repo: Analyze or modify both codebase and documentation, or the entire repository.
+
+RULES:
+
+- Do not include explanations, extra text, or markdown.
+- Always return valid JSON parsable into the specified schema.
+- Ensure "confidence" is a float between 0 and 1.
+"""
+
+planner = """
+You are an autonomous planning agent in a multi-agent system.
+
+Your responsibility:
+- Select the most appropriate operations to fulfill the user request.
+- Do NOT invent new operations.
+- Use ONLY the operations provided in the list.
+
+Strict rules:
+- You MUST return a valid JSON object.
+- The JSON MUST conform exactly to the following schema:
+
+{{
+  "operations": ["string"],
+  "reasoning": "string"
+}}
+
+Additional constraints:
+- "operations" must be a list of operation names.
+- Do NOT include any explanations outside of the JSON.
+- Do NOT include markdown.
+- If no operations are applicable, return an empty list.
+
+You are NOT allowed to reorder operations by logic — ordering is handled externally.
+"""
+
+detect_arguments = """
+You are an intelligent assistant responsible for extracting the required arguments for specific operations from the user request.
+
+Your responsibilities:
+- For each operation extract them directly from the user request.
+- If the user request contains relevant values for the arguments, return them.
+
+Strict rules:
+- You MUST return a valid JSON object.
+- The JSON MUST conform exactly to the following schema:
+
+{{
+  "operation_name": {{"arg1": value1, "arg2": value2, ...}},
+  "operation_name_2": {{"arg1": value1, "arg2": value2, ...}}
+}}
+
+Additional constraints:
+- Only include the necessary arguments for each operation.
+- Do NOT include any explanations outside of the JSON.
+- Do NOT include markdown.
+- If the user request contains values for an operation's arguments, include them in the response.
+- If no relevant arguments are found for a given operation, skip that operation from the JSON.
+"""
+
+pr_summarizer = """
+You are an assistant that writes concise and professional GitHub Pull Request descriptions.
+
+Your task:
+- Summarize repository changes based on structured operation events
+- Be factual, neutral, and clear
+- Do NOT invent changes
+- Do NOT mention internal tooling or agents
+- Prefer bullet points if multiple changes exist
+
+Strict rules:
+- You MUST return a valid JSON object.
+- The JSON MUST conform exactly to the following schema:
+
+{{
+  "summary": "text",
+}}
+"""

{osa_tool-0.2.6 → osa_tool-0.2.7}/osa_tool/config/settings/arguments.yaml

@@ -31,11 +31,6 @@ arguments:
       with language-specific suffixes (e.g., README_ru.md, README_zh.md).
     example: Russian Chinese
 
-  delete_dir:
-    aliases: [ "--delete-dir" ]
-    type: flag
-    description: "Enable deleting the downloaded repository after processing."
-
   ensure_license:
     aliases: [ "--ensure-license" ]
     type: str
@@ -103,6 +98,16 @@ arguments:
     description: "Check whether the experiments proposed in an attached documentation file can be reproduced using the selected repository."
 
 settings:
+  use_single_model:
+      aliases: [ "--use-single-model" ]
+      type: flag
+      description: "Use the same model for all tasks (from default configuration)."
+
+  config_file:
+    aliases: [ "--config-file" ]
+    type: str
+    description: "Path to custom configuration file (TOML format)."
+
   no_fork:
     aliases: [ "--no-fork" ]
     type: flag
@@ -113,6 +118,11 @@ settings:
     type: flag
     description: "Do not create a pull request to the target repository."
 
+  delete_dir:
+    aliases: [ "--delete-dir" ]
+    type: flag
+    description: "Enable deleting the downloaded repository after processing."
+
   repository:
     aliases: [ "-r", "--repository" ]
     type: str
@@ -175,6 +185,26 @@ settings:
       Specific LLM model to use. See available providers and models:
       https://github.com/aimclub/ProtoLLM/tree/main/protollm/connectors
 
+  model_docstring:
+    aliases: [ "--model-docstring" ]
+    type: str
+    description: "Specific LLM model for docstring generation tasks."
+
+  model_readme:
+    aliases: [ "--model-readme" ]
+    type: str
+    description: "Specific LLM model for README generation tasks."
+
+  model_validation:
+    aliases: [ "--model-validation" ]
+    type: str
+    description: "Specific LLM model for validation tasks."
+
+  model_general:
+    aliases: [ "--model-general" ]
+    type: str
+    description: "Specific LLM model for general tasks such as About section generation or reorganization."
+
   temperature:
     aliases: [ "--temperature" ]
     type: float