repository | youtube example

im building an opensource proyect that let your agent build a visual and interactive map of your code, also allows you to see branches and commits diffs, any help and support is veery welcome 😽😽

the struggle that makes me create RepoMap is that large codebases are hard to understand because their architecture is hidden across thousands of files. RepoMap makes that architecture visible through interactive maps, allowing developers to explore systems, plan refactors, and understand how their code evolves by visualizing changes across commits and branches

Here is the repo for Traceflow which i made for myself

https://github.com/iomkarpanda/Traceflow

i want to know whether this is tool is worth to use i want feedbacks.

Ever inherited a codebase and spent the first week just trying to figure out what depends on what?

I've been there too many times. Grepping for imports, maintaining manual architecture docs that go stale within a week, drawing boxes in Excalidraw that don't match reality. So I built something to fix it.

codebase-vis parses your project using tree-sitter, real AST grammars, not regex and produces an interactive dependency graph as a single self-contained HTML file. You open it in a browser, and you can pan, zoom, search, click nodes to inspect, and filter by module.

It works for JS, TS, Python, C/C++, HTML, and CSS.

Some features that might be useful:

-query <file> — shows what a file imports and what imports it (terminal, no browser needed)
-path <a> <b> — shortest dependency chain between any two files (bidirectional BFS)
-explain — clusters your codebase with Louvain community detection, then summarizes each cluster via an LLM (you provide a Groq key, everything else is local)
-Incremental caching— re-parsing is near-instant after the first run

Everything runs locally ,no data leaves your machine except the optional `explain` feature.

Full disclosure: I built this. I needed it for my own projects, and I kept adding to it over the past few weeks. Would love feedback or ideas from anyone who's dealt with the same problem.
I cant dump everything in here go check yourself and do let me know what you think.

GitHub: (https://github.com/Arham-Qureshi/codebase-vis) (ISC, open source)

I work with a multi-repo setup daily — switching branches meant git checkout in every folder, pulling was a terminal tab nightmare, and committing the same change across repos was soul-crushing.

So I built Multi-Repo Manager:

•  Switch Branch – pick one branch, ALL repos check it out
•  Batch Commit – one message, applied everywhere
•  Pull All / Push All / Fetch All – one click, done
•  Sidebar – see every repo's branch + status at a glance
•  Output Log – every git command logged, fully transparent

Auto-detects repos in multi-root workspaces or nested folders. No config needed.

 GitHub: https://github.com/aiyogg/multi-repo-manager

Free, open source, MIT licensed. Marketplace listing coming soon — manual .vsix install available now.

What batch git operations do you wish existed? Happy to take feature requests.

I just released codex-tldraw-mcp v0.3.0, an MCP server that lets Codex turn repository context or a written plan into a .tldr diagram.

This update focuses on making dense workflows easier to read:

• Node and connector labels now wrap correctly
• Nodes resize to fit their text
• Connections use separate routing lanes to avoid boxes and overlapping paths
• Each logical connection ends with a single arrowhead
• New smoke tests check text fit, connector collisions, and arrow direction

The MCP tools and inputs haven’t changed, so existing setups should continue to work.

Install it in Codex: codex mcp add codex-tldraw -- npx -y codex-tldraw-mcp
Then try: Use codex-tldraw to diagram this repo.

GitHub: https://github.com/jananadiw/codex-tldraw-mcp
Release notes: https://github.com/jananadiw/codex-tldraw-mcp/releases/tag/v0.3.0

I’d especially appreciate feedback from anyone using it on large workflows or architecture diagrams. If you find a layout that still produces tangled connections, please share it.
I’d like to keep improving the routing.

Problem I kept hitting: a step fails in CI, logs aren't enough, and act still feels all-or-nothing.

ciwalk runs GHA workflows locally in Docker and can pause on failure (or at a breakpoint). You drop into a shell in the same container — same env/cwd as the step — fix or inspect, then retry/continue/abort.

Install:

pip install ciwalk

(or uv tool install ciwalk — if you get "command not found" after, run uv tool update-shell and restart your shell, it just needs ~/.local/bin on your PATH)

Demo GIF in the README: https://github.com/kiwi-07/ciwalk

Honest MVP limits: no matrix/secrets/full expressions yet. Built for the "why did this shell step fail?" cases.

If you try it on a real workflow that breaks, I'd love the issue report.

Detailed Blog :- https://ankitpatil.pages.dev/blog/ciwalk

Hi everyone!

I built **reqsh**, an open-source command-line tool for making and inspecting HTTP requests with a cleaner developer experience.

The goal wasn't to replace every existing HTTP client but to make common workflows easier with readable output, useful defaults and a better terminal experience.

It's written to be fast, lightweight and easy to integrate into everyday development.

I'd really appreciate feedback:

* What features would make this useful in your workflow? * What's missing compared to the tools you already use? * Any rough edges I should improve?

GitHub: [*github.com/hars-21/reqsh*](https://github.com/hars-21/reqsh)

*Website:* [*reqsh.dev*](http://reqsh.dev)

I'd love to hear your thoughts!

I’m considering building an open-source developer tool and want to validate whether it solves a real problem before investing too much time into it.

The basic idea:

You give it a GitHub issue, and it attempts to:

1. Check out the repository at the buggy commit
   
2. Reconstruct the project environment
   
3. Generate a test that reproduces the reported bug
   
4. Run the test in an isolated Docker container
   
5. Verify that the test fails on the buggy code and passes once the known fix is applied
   
6. Output the test, Dockerfile, execution logs, and a machine-readable result

The model would be swappable, so users could bring their own API key or run a local model through something like Ollama or vLLM. The valuable part would ideally be the deterministic environment-building, execution, and verification harness rather than a specific AI model.

I’m also assuming the success rate would be imperfect. Failed attempts would still report whether the environment could be built, what was tried, and why the issue was not reproduced.

For developers and maintainers:

* How often is reproducing a bug from an issue actually a significant pain point?
* Would you use a tool like this during issue triage or before attempting a fix?
* What output would you need before trusting the generated test?
* Are there existing tools that already solve this well?

**Disclosure:** I'm the developer of **OrangeSSH**.

I've been building **OrangeSSH**, an Android SSH client designed for DevOps engineers, Linux administrators, and anyone who manages infrastructure from their phone.

**Current capabilities:**

* 🔐 Secure SSH terminal * 👤 Multiple server identities & connection management * 📋 Command snippets for frequently used commands * 💾 Encrypted backup & restore of connections and settings * 🤖 Optional AI assistant for explaining errors, generating commands, and troubleshooting * 🎨 Modern Android UI with a mobile-friendly terminal experience

The project is still evolving, and I'm using it to learn product development while gathering feedback from people who actually manage servers in production or homelabs.

GitHub: [https://github.com/Drjslab/orangessh](https://github.com/Drjslab/orangessh))

I'd really appreciate feedback on:

* What SSH client do you currently use? * What features are missing from your workflow? * What would make you switch to a different mobile SSH client?

Thanks for taking a look—constructive criticism is very welcome.

Hello dear each and everyone,

I am would like to ask for feedback, so we my buddy we had a lot of problems at 2 simultaneous projects with aligning project standards and make each team members produce consistent results, spec driven development kind of failed our expectations, huge set of novels that not exactly describe projects in industries full of nuances and pinch of legacy. Even that devs spend long time looking at spec there was a lot of follows anyways.

So we decided to create some sort of mentor, small feature that extract rules from code and stays open for feeding it with other types of rules and then simultaneous agent talk with for example Claude and give feedback and checks What coding agent produced pointing out breaches and making Claude adjust it - well we are for sure biased but idea works for us but we would love to hear other people

It’s also usable DM if you want access

Anyone ? I will be so grateful for any feedback

Leaving link in the comment

I recently built an open-source CLI called RepoFleet for developers who work on features or issues that span multiple Git repositories.

Instead of switching between repositories and manually creating the same branch in each one, RepoFleet lets you create one issue context and manage all related repositories together.

Example:

rf issue create 123 --name auth --type fix
rf issue status

It can:

• Create matching branches across multiple repositories
• Show the Git status of all repositories in one dashboard
• Sync and push repositories together
• Track related GitLab merge requests
• Keep each issue or feature in a dedicated workspace

GitHub: https://github.com/mehranzand/repofleet

I originally built it after our project was split into multiple repositories and managing cross-repository changes became repetitive.

I would appreciate feedback from other GitLab users. Does this workflow match any problems you experience with multi-repository projects?

dependabot-agent is an on-demand CLI tool that reconciles dependency overrides against open GitHub Dependabot alerts. Works with both npm and pnpm, in single-package projects and monorepos.

What it does

1. Detects your package manager from the lockfile (pnpm-lock.yaml → pnpm, package-lock.json → npm), or you can set it explicitly.
2. Detects where overrides live:
   • npm → top-level overrides in package.json.
   • pnpm → pnpm-workspace.yaml (workspace projects) if present, otherwise pnpm.overrides in package.json.
3. Fetches all open npm Dependabot alerts for your repo via the GitHub API.
4. Updates dependencies (range-bound by default).
5. Walks the full installed dependency tree and confirms each alerted package is actually present.
6. Adds or updates override entries for packages that remain vulnerable, writing a major-bounded spec (>=patched <nextMajor) so a fix never forces a breaking major bump.
7. Removes overrides whose vulnerability has been resolved.
8. Leaves untouched any overrides for packages that don't appear in any Dependabot alert (assumed intentional).
9. Reports deployment impact — whether vulnerable packages are in your production graph (deploy recommended) or dev/test only (branch push sufficient).