eladkaplan

I maintain several open-source projects and was spending hours every day triaging GitHub notifications — context-switching between repos, deciding what's urgent, reviewing PRs without missing breaking changes.

Ossue pulls issues, PRs, and discussions from all your repos into one local inbox. AI analyzes each item automatically: structured triage for issues (bug vs feature, priority, area), code review verdicts for PRs (with breaking change detection), and discussion summaries. You can customize the AI's review criteria per project.

It also has a "notes to issues" workflow, brain dump a rough idea, AI structures it into a proper GitHub issue with title, labels, and priority, then publish directly.

AI coding agents are powerful but they don't hesitate before running rm -rf /, kubectl delete namespace production, or terraform destroy. shellfirm adds a safety layer that catches risky commands before they execute.

How it works with AI agents:

One command to set up: shellfirm connect claude-code

This gives you two layers of protection:

1. Hooks – automatic pre-execution checks that block dangerous commands before the agent can run them. The agent can't bypass or ignore these.

2. MCP tools – the agent can proactively ask "is this command risky?" and get back structured risk assessments with severity, blast radius, and safer alternatives.

shellfirm covers 9 ecosystems (git, k8s, terraform, databases, filesystem, etc.) with pattern matching, context detection (SSH, root, production branch), and team policies via .shellfirm.yaml.

Supports Claude Code (hooks + MCP), Cursor, Windsurf, Zed, and Cline.

Written in Rust. Open source.

Tried Intuvo — it transforms CVs into strategic interview blueprints. You upload a resume + job description, and it uses LLMs to: - Reveal strengths & gaps - Flag red flags - Generate tailored interview questions

Feels like a superpower for recruiters or hiring managers.

Curious, would you use something like this in your workflow? What would make it more useful or trustworthy?

We're excited to announce a major release packed with features, improvements, and fixes that will supercharge your Loco experience!

We're thrilled to announce a powerful new version of Loco, packed with features, fixes, and improvements designed to supercharge your development experience!

When I maintained the https://loco.rs project, I often encountered issues with documentation not keeping up with code changes.

To address this, I developed the snipdoc tool, which significantly improved the project's ease of maintaining and validating the docs as part of our CI.

I would love to hear your feedback. Thanks!

Hi all,

Now that we're pretty much solid with Loco (https://loco.rs), the "Rust on Rails" framework, we're taking feedback from the community on what they would expect to see on the UI part.

Should it be React based? Dioxus? Yew?

Happy if anyone would like to chip in with their opinion here:

https://github.com/loco-rs/loco/issues/130

We've just released an initial version of Loco, a Rails inspired framework for Rust. Looking to get feedback, ideas, and contributions! (also, feel free to AMA here)

New shellclear version was released with more detect patterns

shellclear is a security tool that provides a simple and fast way to secure your shell command history. Sensitive data can be stored in your history file when exporting a token of something or running a script with a token. Sometimes those secrets can be visible to others when sharing your terminal / autocomplete command and more.

* Shellclaer can be a shell plugin that shows a summary of sensitive data when opening a new terminal * Get a list of sensitive data found in the history shells * Clear the sensitive information

agree, this is the reason that i wrote it in rust faster easy to maintain unitesting and small binary

shellfirm not changes the shell command, only get the the command and check the pattern. the shell is execute the command.

You really think shell script will be easier? can you elaborate?

this is configurable, depend what you want. the `enter` challenge is not the default. you can configure the challenge

what is your point? do implement the risky command in bash script?

absolutely, it configurable.

run shellfirm config --help and you can changed the challenge

In zshrc is much more easier based on the hooks that you get

Find sensitive data that stored in your shell history

https://github.com/rusty-ferris-club/shellclear

shellfirm not execute the command. it's just get interrupt when you run the command, check the pattern and prompt your a verification. your shell is the executer

In base you need a hook that get the command before your shell execute the command. when the shell get the command interrupt this project execute shellfirm before summation in your shell

Hey this project is very small, and not execution command! only prompt you a verification when detect a risky pattern from a yaml pre-define (default or by you)

You can see the yaml files.

it wrote in rust to make is faster

I agree that the context will be better and I'm planning to add it in the next releases.

How do I save myself from myself?

rm -rf * git reset --hard Before hitting the enter key? kubectl delete ns Stop! you are going to delete a lot of resources And many more!

visit here: https://github.com/kaplanelad/shellfirm

Secrets can be everywhere, even in your shell history commands. I created a small tool that detects and clean those commands from your history. You can even stash your history commands before you share your screen and pop the history when you finish.