Add promptext

[1broseidon]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/1broseidon/promptext
• pkg.go.dev: https://pkg.go.dev/github.com/1broseidon/promptext
• goreportcard.com: https://goreportcard.com/report/github.com/1broseidon/promptext
• coverage service link (codecov, coveralls, etc.): https://app.codecov.io/gh/1broseidon/promptext

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added documentation entry for promptext, a CLI utility for extracting and formatting code context with token counting capabilities for use with AI assistants.

[coderabbitai]

Walkthrough

A new CLI tool entry called "promptext" was added to the Standard CLI category in README.md. The tool is described as extracting and formatting code context for AI assistants with token counting functionality.

Changes

Cohort / File(s)	Summary
Documentation README.md	Added new entry for promptext CLI tool in Standard CLI category with description of code context extraction and token counting capabilities

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single-line addition to documentation with no logic or functional changes
• Minimal context required; straightforward entry in an existing list structure

Poem

🐰 A prompt extract tool joins the CLI crew,
With token counts bright and context so true,
For assistants seeking code context to chew,
README grows richer—hooray, something new! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add promptext' directly and clearly describes the main change—adding a new entry for the promptext package to the README.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56e2cfa and c7a8413.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality
• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (1)

README.md (1)

446-446: Style OK; please confirm category fit.

• Alphabetical position after "pflag" and before "readline" is correct.
• Description is concise, neutral, and ends with a period.

Given "Standard CLI" is described as libraries for building CLIs, double‑check that a CLI tool like promptext belongs here (vs. “Utilities” or “Go Tools”). If current convention accepts tools here (e.g., Dnote), then this is fine.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.