Add killport to Advanced Console UIs

[TNT-Likely]

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):
• pkg.go.dev:
• goreportcard.com:
• coverage service link (codecov, coveralls, etc.):

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.
• I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

Project Information

• Repository: https://github.com/TNT-Likely/killport
• pkg.go.dev: https://pkg.go.dev/github.com/TNT-Likely/killport
• Go Report: https://goreportcard.com/report/github.com/TNT-Likely/killport

Description

Cross-platform CLI to kill processes on ports with interactive mode and system tray support.

Features

• Simple one-command usage: killport 3000
• Interactive TUI mode
• System tray support
• Port protection
• Works on Linux, macOS, Windows

Summary by CodeRabbit

• Documentation
  • Extended the advanced console UIs reference documentation with a newly added command-line library entry. This helpful update provides developers with an expanded selection of resources and tools when designing and building command-line interfaces, enhancing the overall completeness and usefulness of the reference materials available for CLI development.

[coderabbitai]

Walkthrough

A new entry for the killport project was added to the README's Command Line → Advanced Console UIs section. This is a content-only addition to the existing CLI libraries list with no functional changes.

Changes

Cohort / File(s)	Summary
README documentation update README.md	Added killport project entry to the Command Line → Advanced Console UIs section

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Content addition only; verify the killport reference is accurate and formatting is consistent with existing entries

Poem

🐰 A new tool joins the CLI crew,
Killport joins the listings true,
The README grows, page by page,
With helpful tools upon its stage,
Documentation blooms anew! 📝

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "Add killport to Advanced Console UIs" directly and accurately reflects the main change in the pull request. According to the raw summary, a new entry for the killport project was added to the Command Line -> Advanced Console UIs section of the README. The title is concise, specific, and clearly communicates the primary change without vague language, emojis, or noise. A teammate scanning the commit history would immediately understand that this PR adds a new CLI library to a specific section of the awesome-go repository.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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 link: missing
• pkg.go.dev: missing
• goreportcard: missing
• coverage: missing

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

386-386: Entry style OK; confirm section fit.

• Alphabetical order, tone, and ending period look good.
• Please confirm this belongs under “Advanced Console UIs” (generally library-focused). If killport is primarily a CLI app, consider moving it to “Software Packages → Other Software.” Otherwise keep as is.

Optional wording tweak for concision:

- - [killport](https://github.com/TNT-Likely/killport) - Cross-platform CLI to kill processes on ports with interactive mode and system tray support.
+ - [killport](https://github.com/TNT-Likely/killport) - Cross-platform CLI to kill processes by port, with interactive mode and optional system tray.

Also ensure the PR description includes pkg.go.dev, Go Report Card, coverage, release tag, go.mod, and CI links per the checklist.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90f89e3 and 27b9d20.

📒 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). (5)

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