Загрузка видео...

Не удалось загрузить видео

На главную

CODEX SKILL THAT FINDS CODE YOUR APP DOESN’T NEED ANYMORE! I made a Codex skill that scans your codebase and finds code you can potentially remove safely. Scan your project while Codex checks orphan files, unused exports and dependencies, duplicate logic, stale code, dynamic imports, routes, and config references....

Kappaemme1926's profile picture

Kappaemme

4,467 subscribers

39,108 просмотров • 1 месяц назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

CODEX SKILL THAT FINDS COMPLEXITY HOTSPOTS IN YOUR CODEBASE! I made a Codex skill that analyzes your codebase and reports where performance can be improved safely. Scan your project while Codex checks loops, repeated lookups, render-heavy code, N+1 patterns, and places where complexity can potentially be reduced without breaking behavior. -> codebase complexity analysis -> O(n²), O(n*m), repeated scan detection -> before/after complexity estimates -> safe optimization suggestions -> risk level + tests needed -> report-only mode by default -> one-command install Install: npx --yes codex-complexity-optimizer 100% open source. Repo in Bio.
0:26

CODEX SKILL THAT FINDS COMPLEXITY HOTSPOTS IN YOUR CODEBASE! I made a Codex skill that analyzes your codebase and reports where performance can be improved safely. Scan your project while Codex checks loops, repeated lookups, render-heavy code, N+1 patterns, and places where complexity can potentially be reduced without breaking behavior. -> codebase complexity analysis -> O(n²), O(n*m), repeated scan detection -> before/after complexity estimates -> safe optimization suggestions -> risk level + tests needed -> report-only mode by default -> one-command install Install: npx --yes codex-complexity-optimizer 100% open source. Repo in Bio.

Kappaemme

299,213 просмотров • 3 месяцев назад

CODEX SKILL THAT FINDS COMPLEXITY HOTSPOTS IN YOUR CODEBASE! I made a Codex skill that finds performance hotspots, proposes one safe optimization, and proves whether it actually worked. Scan your project while Codex creates a repeatable benchmark, asks for approval before changing any files, runs the tests, and compares real before/after performance. → performance hotspot detection → mandatory approval before edits → repeatable before/after benchmarks → median, p95 + noise analysis → PROVEN / INCONCLUSIVE / REGRESSION verdict → behavior and test verification → native Markdown report → one-command install Install: npx --yes codex-speedup-proof 100% open source. Repo in bio.
0:27

CODEX SKILL THAT FINDS COMPLEXITY HOTSPOTS IN YOUR CODEBASE! I made a Codex skill that finds performance hotspots, proposes one safe optimization, and proves whether it actually worked. Scan your project while Codex creates a repeatable benchmark, asks for approval before changing any files, runs the tests, and compares real before/after performance. → performance hotspot detection → mandatory approval before edits → repeatable before/after benchmarks → median, p95 + noise analysis → PROVEN / INCONCLUSIVE / REGRESSION verdict → behavior and test verification → native Markdown report → one-command install Install: npx --yes codex-speedup-proof 100% open source. Repo in bio.

Kappaemme

22,085 просмотров • 1 месяц назад

CODEX SKILL THAT FINDS YOUR STARTUP’S FIRST CUSTOMERS! I made a Codex skill that analyzes your startup and finds potential customers from real public signals. Paste your startup URL while Codex defines your ideal customer, searches public discussions, qualifies each prospect, and generates a polished report with personalized outreach openers. -> ideal customer profile analysis -> public pain + buying signal research -> evidence-backed prospect shortlist -> fit, timing + reachability scores -> original source links for every prospect -> personalized outreach openers -> polished HTML report -> one-command install Install: npx --yes codex-first-customer-finder-skill 100% open source. Repo in Bio.
0:38

CODEX SKILL THAT FINDS YOUR STARTUP’S FIRST CUSTOMERS! I made a Codex skill that analyzes your startup and finds potential customers from real public signals. Paste your startup URL while Codex defines your ideal customer, searches public discussions, qualifies each prospect, and generates a polished report with personalized outreach openers. -> ideal customer profile analysis -> public pain + buying signal research -> evidence-backed prospect shortlist -> fit, timing + reachability scores -> original source links for every prospect -> personalized outreach openers -> polished HTML report -> one-command install Install: npx --yes codex-first-customer-finder-skill 100% open source. Repo in Bio.

Kappaemme

937,922 просмотров • 1 месяц назад

CODEX SKILL THAT FINDS THE BEST PRICING FOR YOUR STARTUP! I made a Codex skill that analyzes your startup and recommends how you should monetize it. Send it your startup URL while Codex researches competitors, compares pricing models, and recommends concrete plans and price hypotheses. -> monthly vs annual pricing -> subscription, one-time, or lifetime decision -> competitor pricing research -> recommended plans and tiers -> concrete price hypotheses -> value metric + upgrade triggers -> free trial and freemium decision -> lifetime deal risk analysis -> complete Pricing Report (.md) -> actionable 14-Day Pricing Roadmap (.csv) -> no automatic billing changes -> one-command install Install: npx --yes codex-startup-pricing-lab 100% open source. Repo in Bio.
0:37

CODEX SKILL THAT FINDS THE BEST PRICING FOR YOUR STARTUP! I made a Codex skill that analyzes your startup and recommends how you should monetize it. Send it your startup URL while Codex researches competitors, compares pricing models, and recommends concrete plans and price hypotheses. -> monthly vs annual pricing -> subscription, one-time, or lifetime decision -> competitor pricing research -> recommended plans and tiers -> concrete price hypotheses -> value metric + upgrade triggers -> free trial and freemium decision -> lifetime deal risk analysis -> complete Pricing Report (.md) -> actionable 14-Day Pricing Roadmap (.csv) -> no automatic billing changes -> one-command install Install: npx --yes codex-startup-pricing-lab 100% open source. Repo in Bio.

Kappaemme

15,117 просмотров • 1 месяц назад

CODEX SKILL THAT TURNS LOCAL SEARCH INTO CLIENT LEADS! I made a Codex skill that helps find local businesses that may need a website. Search nearby shops, gyms, restaurants, salons, and local activities while Codex checks who has a real website and who only has socials. -> local business prospecting -> website vs social-only checks -> lead scoring -> phone/contact fields -> chat or CSV-style output -> one-command install Install: npx --yes local-client-prospector-skill 100% open source. Repo in Bio.
0:31

CODEX SKILL THAT TURNS LOCAL SEARCH INTO CLIENT LEADS! I made a Codex skill that helps find local businesses that may need a website. Search nearby shops, gyms, restaurants, salons, and local activities while Codex checks who has a real website and who only has socials. -> local business prospecting -> website vs social-only checks -> lead scoring -> phone/contact fields -> chat or CSV-style output -> one-command install Install: npx --yes local-client-prospector-skill 100% open source. Repo in Bio.

Kappaemme

324,749 просмотров • 3 месяцев назад

CODEX SKILL TO BRUTALLY TEST ANY STARTUP IDEA! Most startup ideas sound good. This Codex skill tells you why they probably won’t work. Just give Codex your idea and it pressure-tests it for you -> finds the core assumption -> exposes fatal flaws -> checks if the problem is real -> maps real competitors -> plans your first 10 customers -> defines a 2 week MVP Install: npx --yes codex-startup-pressure-test-skill@latest 100% open source. Repo in bio
0:54

CODEX SKILL TO BRUTALLY TEST ANY STARTUP IDEA! Most startup ideas sound good. This Codex skill tells you why they probably won’t work. Just give Codex your idea and it pressure-tests it for you -> finds the core assumption -> exposes fatal flaws -> checks if the problem is real -> maps real competitors -> plans your first 10 customers -> defines a 2 week MVP Install: npx --yes codex-startup-pressure-test-skill@latest 100% open source. Repo in bio

Kappaemme

512,875 просмотров • 3 месяцев назад

Someone paid $6,000 (!) to get OpenClaw setup. So I built a free, open-source alternative: > OpenClaw Operator It's an agent skill + AGENTS.md/CLAUDE.md file that gives Codex/Claude Code the playbooks + validation flow needed to configure your local OpenClaw install. You open your OpenClaw repo/workspace in your coding agent and say things like: - “set up a cron job” - “create a custom skill” - “fix my provider config” - “troubleshoot this install and validate it” Nothing magical. Uses context from the OpenClaw open-source repo + docs to provide an effective skill. Includes: - SKILL.md - AGENTS.md/CLAUDE.md - validation checklist - task playbooks Free and open source. Contributions welcome. Demo below. Repo in reply.
0:20

Someone paid $6,000 (!) to get OpenClaw setup. So I built a free, open-source alternative: > OpenClaw Operator It's an agent skill + AGENTS.md/CLAUDE.md file that gives Codex/Claude Code the playbooks + validation flow needed to configure your local OpenClaw install. You open your OpenClaw repo/workspace in your coding agent and say things like: - “set up a cron job” - “create a custom skill” - “fix my provider config” - “troubleshoot this install and validate it” Nothing magical. Uses context from the OpenClaw open-source repo + docs to provide an effective skill. Includes: - SKILL.md - AGENTS.md/CLAUDE.md - validation checklist - task playbooks Free and open source. Contributions welcome. Demo below. Repo in reply.

Dan McAteer

17,809 просмотров • 5 месяцев назад

CODEX SKILL THAT TURNS CUSTOMER FEEDBACK INTO A ROADMAP! Most feedback analysis stops at positive or negative. I made a Codex skill that turns support tickets, interviews, surveys, reviews, sales calls, and churn notes into evidence-backed product priorities and credible customer proof. Give it your feedback files and Codex maps recurring pains, ranks what to build next, and links every recommendation back to exact evidence IDs. It keeps four things separate: -what customers said -the underlying problem -what to validate or build next -what you can honestly claim -> feedback clustering with source traceability -> product opportunity scoring -> Now / Next / Later roadmap -> customer proof + case-study candidates -> objections, churn risks, and unsupported claims -> searchable Startup Customer Evidence Map -> privacy-first quote and consent handling -> one-command install What would you analyze first: support tickets, interviews, or churn notes? Install: npx --yes startup-feedback-engine@latest 100% open source. Repo in Bio.
0:36

CODEX SKILL THAT TURNS CUSTOMER FEEDBACK INTO A ROADMAP! Most feedback analysis stops at positive or negative. I made a Codex skill that turns support tickets, interviews, surveys, reviews, sales calls, and churn notes into evidence-backed product priorities and credible customer proof. Give it your feedback files and Codex maps recurring pains, ranks what to build next, and links every recommendation back to exact evidence IDs. It keeps four things separate: -what customers said -the underlying problem -what to validate or build next -what you can honestly claim -> feedback clustering with source traceability -> product opportunity scoring -> Now / Next / Later roadmap -> customer proof + case-study candidates -> objections, churn risks, and unsupported claims -> searchable Startup Customer Evidence Map -> privacy-first quote and consent handling -> one-command install What would you analyze first: support tickets, interviews, or churn notes? Install: npx --yes startup-feedback-engine@latest 100% open source. Repo in Bio.

Kappaemme

138,192 просмотров • 24 дней назад

This GitHub repo is gold for anyone running Claude Code/ Codex / Any coding agent at all. My usage limits almost last double since I started using this. An open source context layer that stops your agent from reading 40 files to answer one question. No API key, no billing, no rate limit tiers. Benchmarked against Claude Code baseline: 27x token efficiency, 36% lower cost, 89% fewer file reads, 49% fewer tool calls. Every number is reproducible, the harness is in the repo. 3.5k+ stars. 50k+ pip installs, 30+ contributors, works with Claude Code, Cursor and VS Code out of the box. pip install repowise and point it at your codebase.
0:20

This GitHub repo is gold for anyone running Claude Code/ Codex / Any coding agent at all. My usage limits almost last double since I started using this. An open source context layer that stops your agent from reading 40 files to answer one question. No API key, no billing, no rate limit tiers. Benchmarked against Claude Code baseline: 27x token efficiency, 36% lower cost, 89% fewer file reads, 49% fewer tool calls. Every number is reproducible, the harness is in the repo. 3.5k+ stars. 50k+ pip installs, 30+ contributors, works with Claude Code, Cursor and VS Code out of the box. pip install repowise and point it at your codebase.

Srishti

12,998 просмотров • 1 месяц назад

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.
0:22

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,505 просмотров • 2 месяцев назад

NVIDIA just dropped free API keys for every top AI model You don't need your own GPU and you don't pay per token. GLM-5.2, MiniMax, Kimi, DeepSeek, OpenAI, all running on NVIDIA's servers, called through a normal API. Link: How to use one: 1. Create a free NVIDIA account. 2. Pick a Free Endpoint model and open its Build tab. You'll see ready-to-copy code with the base URL 3. Hit Generate API Key, copy it and paste that base URL and key into Claude Code, Cursor, or Cline. Bonus: NVIDIA also dropped 237 official skills that install into Claude Code and Codex in one command. Bookmark this.
0:24

NVIDIA just dropped free API keys for every top AI model You don't need your own GPU and you don't pay per token. GLM-5.2, MiniMax, Kimi, DeepSeek, OpenAI, all running on NVIDIA's servers, called through a normal API. Link: How to use one: 1. Create a free NVIDIA account. 2. Pick a Free Endpoint model and open its Build tab. You'll see ready-to-copy code with the base URL 3. Hit Generate API Key, copy it and paste that base URL and key into Claude Code, Cursor, or Cline. Bonus: NVIDIA also dropped 237 official skills that install into Claude Code and Codex in one command. Bookmark this.

Yarchi

62,979 просмотров • 1 месяц назад

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this
1:15

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

self.dll

19,794 просмотров • 4 месяцев назад

How to build an AI SEO Loop with Claude Code. I just launched a Free course on how to setup Claude Code, Hermes, Codex or any agent to become your Chief SEO that gets you customers on autopilot. Comment "Loop" and I'll send an access in your DMs. You'll learn: - How to install the SEO Skill. - Audit and Fix your website through Google Search Console. - Find keywords that convert. - Publish content automatically. - Track your positions on Google and your AI visibility. - Get recommended by AI. - and more bonuses.
7:36

How to build an AI SEO Loop with Claude Code. I just launched a Free course on how to setup Claude Code, Hermes, Codex or any agent to become your Chief SEO that gets you customers on autopilot. Comment "Loop" and I'll send an access in your DMs. You'll learn: - How to install the SEO Skill. - Audit and Fix your website through Google Search Console. - Find keywords that convert. - Publish content automatically. - Track your positions on Google and your AI visibility. - Get recommended by AI. - and more bonuses.

Florian Darroman

23,980 просмотров • 2 месяцев назад

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.
29:06

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.

shmidt

51,155 просмотров • 1 месяц назад

every App Store rejection costs you 2-5 days. so we built a cli that scans your iOS app against apple's guidelines before you submit. > payment & IAP compliance > privacy manifests & data declarations > required sign-in & account deletion flows > metadata & completeness checks > binary validation now with a added cloud device feature, so it validates full user flows, not just the binary. made it a claude code and codex skill. it fixes every issue it finds. scan, fix, repeat until it passes.
0:33

every App Store rejection costs you 2-5 days. so we built a cli that scans your iOS app against apple's guidelines before you submit. > payment & IAP compliance > privacy manifests & data declarations > required sign-in & account deletion flows > metadata & completeness checks > binary validation now with a added cloud device feature, so it validates full user flows, not just the binary. made it a claude code and codex skill. it fixes every issue it finds. scan, fix, repeat until it passes.

Landseer Enga

648,340 просмотров • 1 месяц назад

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!
1:38

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!

Superdaddy

43,285 просмотров • 5 месяцев назад

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:
4:42

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:

Santiago

296,637 просмотров • 10 месяцев назад

How to manage secrets with worktrees: Files that are untracked in Git will NOT be copied over to new worktrees (Codex, Claude Code, & Conductor included) Claude Code introduced .worktreeinclude, which uses glob syntax to copy untracked files into new directories - these can be .env files, secrets, or anything else you don't want in Git (s/o ClaudeDevs) Here's how to get started: 1. Add .worktreeinclude to your project 2. Specify which files to copy (same syntax as .gitignore) 3. New worktrees will have these files copied over automatically Conductor supports .worktreeinclude for Claude AND Codex - one config, two harnesses! We also have a setting called "files to copy" if you don't like random dotfiles cluttering up your projects :) Here's how you can use "files to copy" and .worktreeinclude to worktreemax
2:12

How to manage secrets with worktrees: Files that are untracked in Git will NOT be copied over to new worktrees (Codex, Claude Code, & Conductor included) Claude Code introduced .worktreeinclude, which uses glob syntax to copy untracked files into new directories - these can be .env files, secrets, or anything else you don't want in Git (s/o ClaudeDevs) Here's how to get started: 1. Add .worktreeinclude to your project 2. Specify which files to copy (same syntax as .gitignore) 3. New worktrees will have these files copied over automatically Conductor supports .worktreeinclude for Claude AND Codex - one config, two harnesses! We also have a setting called "files to copy" if you don't like random dotfiles cluttering up your projects :) Here's how you can use "files to copy" and .worktreeinclude to worktreemax

matt palmer

28,298 просмотров • 2 месяцев назад

Claude Code Templates just hit 100+ Skills on Installing is easy - one click to copy the install command, paste it in your project's .claude folder, done. - 67K npm installs - 13K+ GitHub stars - fully open source Thanks to the community for contributing Skills and components. In the video I show how to add a Data Privacy Compliance Skill to your project.
0:36

Claude Code Templates just hit 100+ Skills on Installing is easy - one click to copy the install command, paste it in your project's .claude folder, done. - 67K npm installs - 13K+ GitHub stars - fully open source Thanks to the community for contributing Skills and components. In the video I show how to add a Data Privacy Compliance Skill to your project.

Daniel San

164,637 просмотров • 8 месяцев назад

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,177 просмотров • 2 месяцев назад