readme formatting

[gitcommitshow]

No description provided.

[contributor-support-github-app]

Thank you for contributing this PR.
Please sign the Contributor License Agreement (CLA) before merging.

[contributor-support-github-app]

Thank you @gitcommitshow for contributing this PR.
Please sign the Contributor License Agreement (CLA) before merging.

[contributor-support-github-app]

Analysis Summary

The README.md file for gcs-cli currently serves as an internal development checklist rather than user-facing documentation. It completely lacks context about the project's purpose, installation instructions, or usage examples. This makes it very difficult for a new user or potential contributor to understand what the project is or how to get started. The content mixes feature lists with development tasks and bug reports, which violates the Diátaxis principle of maintaining clear boundaries between different types of information. The document needs a fundamental restructuring to be effective.

Objective Rating Score

Category	Score (0-100)
Technical Accuracy Score	90
Comprehensibility Score	20
Overall Score	48

Mistake Counts:

• Major Comprehensibility: 2
• Comprehensibility: 2
• Minor Technical Accuracy: 1

Actionable Suggestions

File: README.md

1. Major Comprehensibility: Add a project description at the top. Explain what "Git-Commit-Show" is and what this CLI tool helps users do. This provides essential context (Explanation).
2. Major Comprehensibility: Create dedicated sections for "Installation" and "Usage". Provide step-by-step instructions for users to install the tool and its dependencies, and show basic command examples (How-To Guide).
3. Comprehensibility: Move the "TASKS" and "BUGS" sections to a separate CONTRIBUTING.md file or into the repository's issue tracker. This content is for contributors, not end-users, and should be separated.
4. Comprehensibility: Rewrite the "Features" section to be more descriptive. Instead of a simple checklist, briefly explain what each feature does (e.g., "Stream masterclass videos directly in your media player").
5. Minor Technical Accuracy: Correct the malformed markdown link for StreamLink. It should be [StreamLink](https://streamlink.github.io).

Strengths

• The document provides a clear, albeit brief, list of the project's current and planned features.
• It tracks development tasks and known bugs, which is useful for project management, even if misplaced in a README.