Translate tool descriptions to English: shell, file search and app tools
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- developer-experience
Research direction
Read docs/TOOL-STYLE.md, then update the tool and parameter descriptions in alice/tools/shell.py, alice/tools/findfiles.py, and alice/tools/apps.py. Keep names, parameters, defaults, behavior, and user-facing return messages unchanged. Run the related pytest selection and ruff check alice; done means all specified descriptions are concise English and both checks pass.
Written by the indexing model from the issue text.
Description
Part of #213. The tool definitions sent to the model are still written in Turkish. Translate them to English in:
alice/tools/shell.pyalice/tools/findfiles.pyalice/tools/apps.py
What to translate: each tool's description and the description of its parameters (the JSON schema passed to Tool(...)).
What not to change:
- tool names, parameter names, types and defaults;
- messages the tool returns to the user (those are user-facing text, handled by #214);
- behavior: this is a text-only change.
Follow docs/TOOL-STYLE.md: say what the tool does and when to use it, short and concrete. Then run the related tests, for example pytest -q tests -k "shell or findfiles or apps", and ruff check alice.
A good first contribution: a few dozen strings, no logic. See CONTRIBUTING.md.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 112
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine
-
agent good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#251 ·
Maintainers usually reply within 1 day
-
agent good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#250 ·
Maintainers usually reply within 1 day
-
agent good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#248 ·
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#247 ·
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine#246 ·
Maintainers usually reply within 1 day
All issues in Viox-Development/Artificial-Logic-and-Intelligence-Computation-Engine
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
aws-samples/sample-spec-driven-presentation-maker#648 ·
Maintainers usually reply within 1 day
-
firestore: enable live window.yaml pipeline system tests once add_window_fields is in productionOpen
Difficulty 1/5 Under an hour Newbie friendliness 64/100
googleapis/google-cloud-python#19115 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Feyisara2108/stellargive#1377 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day