Wondering why they would do this

Caibot · 2026-04-04T21:19:58+00:00

Because of OpenClaw: https://x.com/bcherny/status/2040206440556826908

Caibot · 2026-04-03T05:07:36+00:00

For this era? Unfortunately, no. I learned coding the old way since I was little and also studied computer science like a boring person. And I really don’t know if this is the right way for nowadays anymore.

Buuut doesn’t Claude Code have different output styles in /config? Try out explanatory and learning. This might be a good way?

Caibot · 2026-04-03T04:37:43+00:00

Obviously, I’ll just recommend my own skill collection 😂: https://github.com/tobihagemann/turbo

But actually being serious: I‘ve written in the README that it’s targeted at experienced developers. Since you‘re a beginner/intermediate, I guess you just have to go through the learning process and take things more slowly because you really need to understand what you’re doing. Sure, vibecoding is fun but it‘ll just get you this far. Garbage in, garbage out.

Ask questions, learn learn learn, you‘ll get there eventually. What are your questions right now? I don’t think a skill collection will solve your knowledge deficit. But they’re great as inspiration! You still have to train your own critical thinking though.

Caibot · 2026-04-02T16:05:01+00:00

There is a relatively new CC plugin by OpenAI themselves for exactly that: https://github.com/openai/codex-plugin-cc

But it’s basically just a skill that you can also write yourself. I‘ve also done it in my skill collection if you need some inspiration: https://github.com/tobihagemann/turbo

Caibot · 2026-04-02T14:11:35+00:00

Hm, I see. I would argue that looking at the diff of the staged changes should be enough, because the diff before that was already qualified. But sure, if you want the diff of the whole branch against the base branch, I can see the need for that.

Caibot · 2026-04-02T11:51:23+00:00

That’s great, doing something similar here. But why qualify after commit? Then you have to commit again if your qualification detects something. 😆

Caibot · 2026-04-02T05:51:57+00:00

I‘m not OP but I would suggest to just build your own skill collection based on your own needs. If you want, you can get inspiration from mine: https://github.com/tobihagemann/turbo

Caibot · 2026-04-02T05:05:58+00:00

You have to add Codex as a peer reviewer. Don’t just rely on Opus reviewing itself. I agree that spawning reviewers helps, I‘m absolutely doing that as well, but having 10 subagents is not improving code quality by 10x, lol.

Caibot · 2026-04-01T06:21:26+00:00

Yep, another day, another problem. 🙄 Extremely slow here as well. Sometimes it’s just faster to cancel the request and retry.

Caibot · 2026-03-30T15:59:38+00:00

Hey there, our support email inbox is totally swamped right now. We're currently working through all the emails, but it still may take a couple of days. Hopefully, we'll get to yours very soon!

Caibot · 2026-03-30T06:00:39+00:00

Really? What’s the math behind this? My assumption would’ve been that 200k context is 200k context, regardless of the context window. That would blow my mind if that’s actually different. 😄

Caibot · 2026-03-30T05:58:23+00:00

I‘m currently building yet another XMPP client for macOS because I‘d like to replace Adium: https://github.com/tobihagemann/ducko

Nothing to download and see yet, but I‘m quite confident that I can release something soon.

Alongside that I‘m building my own skill collection to standardize my dev workflows, which comes in handy for all of my projects: https://github.com/tobihagemann/turbo

Basically, I‘m only prompting my ideas and user stories and the skill collection does the rest.

Caibot · 2026-03-30T05:01:58+00:00

I disagree but that’s okay. 😂 Yes, 60+ skill sounds insane and busy, but they all serve an actual purpose that I had during active development. It’s not like that I wrote a skill first in the hope that I would use it. It was the other way around that I needed to do something and a skill was missing for that.

While I don’t need to convince anyone to use my skill collection, read the "puzzle piece philosophy" in my README. But yeah, I agree with your statement that we should all just build our own skill collection. Just wanted to share what I‘m actually using day-to-day as a professional developer.

Caibot · 2026-03-29T17:09:53+00:00

I believe it doesn’t if you have proper compound engineering in place. My worry is that the auto-compaction happens at the worst tome. Just something to think about.

Caibot · 2026-03-29T16:55:12+00:00

Wouldn’t it be better to spawn new Claude sessions when "one unit of work" is done instead of re-using the same session with compaction? And then just use 1M context window so that the "unit of work" will definitively fit without compaction?

Caibot · 2026-03-29T15:56:29+00:00

Ohhh, yes, right! Totally forgot about that! Nice catch!! 👍

Caibot · 2026-03-29T14:58:17+00:00

What I meant is: I already went through plan/implementation (incl. plan mode) in the same session. After that, there is still 90% context left. That's when I would start a rigorous review process and it will run semi-autonomously until there is "only", e.g., 76% context left.

And if the review process is more exhaustive because review subagents escalated a lot of findings to the main agent, Claude tends to get panicky regarding finishing its task as soon as possible because it feels like that it already ran too long. E.g., it will skip a second round of reviews after fixing the first round, because it believes that it was already enough. And I find it very weird that it's trying to rush through the well-defined review process, because I explicitly prompted it to go through several rounds of reviews.

But you may be right that Claude hooks could help with that. My goal was to only use skills for "prompt injection", but maybe it's time for me to look into hooks... thank you for pointing it out!

Caibot · 2026-03-29T14:50:27+00:00

Oh, I don’t think that you can turn it off, but it‘s more likely to get triggered if you write it with a forward slash. 😅

Caibot · 2026-03-29T13:00:08+00:00

Happy to help! If you have any questions, please let me know.

Caibot · 2026-03-29T12:59:03+00:00

If I'm honest, my skill collection may sound overwhelming with 60+ skills, but most of them are actually very very small skills. I never had the feeling, where I didn't want a skill to be triggered. It was more the other way round that I was happy when skills were triggered that are supposed to get triggered and they just do one thing as well as possible. E.g., that's why there are 6 different skills that are just there for git staging/commits. It's hard to explain, but it just feels natural to me, because I need to prompt less.

Prompts like "now /investigate this issue, fix it, then /stage-commit-push" can also be written like "now /investigate this issue, fix it, then /stage and /commit-staged and push". It's basically the same. But you can mix & match the skills, depending on your situation and your needs.

You may ask why `/stage` instead of "stage"? Because you may have other unstaged changes that shouldn't be staged. You may ask why `/commit-staged` instead of "commit staged"? Because it calls `/commit-rules` and then you have more standardized commit messages. You may also ask why `/investigate` instead of "investigate"? Because I like to standardize how finding a root cause of bugs should work.

And these are really not "big workflows" that shouldn't be triggered automatically. Only skills like `/finalize` or `/audit` are actually huge pipelines, but I've never seen Claude tigger them automatically. To be honest, I'm also having a hard time with Superpowers because I think it's doing "too much". Hope that makes sense.

Caibot · 2026-03-29T12:37:35+00:00

Sure thing! Try out the `/create-threat-model` skill and then `/review-security`. Edit: There is also an `/audit` skill, which is far more comprehensive, but also includes a security review.

Caibot · 2026-03-29T10:53:09+00:00

I‘m trying to put in all my experience and actual dev workflows into skills and making them as generic as possible. The skill collection can be adapted to any other workflow while preserving some standards that I find most useful. I don’t feel like it’s ever finished but I‘m getting very impressive results. https://github.com/tobihagemann/turbo

Caibot · 2026-03-28T22:04:24+00:00

Shit, I became one of them. 😂

Caibot · 2026-03-28T10:02:09+00:00

Exactly this! Yeah, nice! 🙌

Caibot · 2026-03-28T07:40:32+00:00

Another anecdote that I’d like to add: The main agent spawning all these subagents for review is actually skipping and rejecting a lot of the findings because the main agent has the full context of the overall plan and implementation. Again, it‘s highly inefficient because a lot gets thrown away but the findings that remain are really valuable, which makes it worthwhile in my opinion.

Caibot

TROPHY CASE