shareAI-lab / shareAI-lab/learn-claude-code

docs(s02): explain why specialized tools are needed when Bash can do the same work

Open Beginner friendly
#549 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
77.2k
Forks
12.4k
Avg merge
2d 5h
Merged PRs (30d)
6

Description

In s02, Bash can already read, write, edit, and find files.
As a learner, I was confused about why the agent adds read_file,
write_file, edit_file, and glob.

I suggest adding a short explanation:
specialized tools do not add new capability, but provide structured
inputs, reduce shell quoting errors, and make future permission and
logging policies more precise.

This will be a documentation-only change.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the s02 lesson documentation and read the section introducing read_file, write_file, edit_file, and glob. Add the requested short explanation about structured inputs, shell quoting errors, and future permission and logging policies. The documentation is done when a learner can understand why these tools exist despite Bash providing similar capabilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.