---
title: "Insights — CommitCycle"
description: "Arguments about running AI coding agents on real repositories: shared context, least privilege, and knowledge that stays true."
url: https://commitcycle.com/insights/
language: en
---

# Insights

> Arguments about running AI coding agents on real repositories: shared context, least privilege, and knowledge that stays true.

Arguments we are willing to be wrong about in public, each dated so you can tell how old the claim is.

- [![](https://commitcycle.com/og/insights/agent-skills-guide-600w.webp)](https://commitcycle.com/insights/agent-skills-guide/)
  ## [The instruction you write once instead of every session](https://commitcycle.com/insights/agent-skills-guide/)
  [What a skill is, why the description is the only part always loaded, what belongs in one versus AGENTS.md, and how to work out why yours is not firing.](https://commitcycle.com/insights/agent-skills-guide/)
- [![](https://commitcycle.com/og/insights/github-for-vibe-coders-600w.webp)](https://commitcycle.com/insights/github-for-vibe-coders/)
  ## [GitHub for people who do not write the code](https://commitcycle.com/insights/github-for-vibe-coders/)
  [Git, GitHub, commits, branches and the four levels of undo — the version control a vibe coder actually needs, and the hacks that recover a lost day.](https://commitcycle.com/insights/github-for-vibe-coders/)
- [![](https://commitcycle.com/og/insights/vibe-coding-setup-600w.webp)](https://commitcycle.com/insights/vibe-coding-setup/)
  ## [Six decisions before your first prompt, and why each one is there](https://commitcycle.com/insights/vibe-coding-setup/)
  [GitHub, a model, a host, a stack, a guardrail and a first prompt — the setup a vibe coder makes once, and what each piece is actually protecting.](https://commitcycle.com/insights/vibe-coding-setup/)
- [![](https://commitcycle.com/og/insights/vibe-coding-first-steps-600w.webp)](https://commitcycle.com/insights/vibe-coding-first-steps/)
  ## [Vibe coding, and the first week that does not end in a mess](https://commitcycle.com/insights/vibe-coding-first-steps/)
  [What vibe coding is, where it genuinely works, where it stops working, and the answers to what people actually ask before their first serious attempt.](https://commitcycle.com/insights/vibe-coding-first-steps/)
- [![](https://commitcycle.com/og/insights/vibe-coding-shared-repository-600w.webp)](https://commitcycle.com/insights/vibe-coding-shared-repository/)
  ## [What breaks when vibe coding meets a repository other people work on](https://commitcycle.com/insights/vibe-coding-shared-repository/)
  [The failure is rarely bad code. It is code that is locally reasonable and globally wrong, because the convention it broke was never written down.](https://commitcycle.com/insights/vibe-coding-shared-repository/)
- [![](https://commitcycle.com/og/insights/what-to-move-out-of-obsidian-600w.webp)](https://commitcycle.com/insights/what-to-move-out-of-obsidian/)
  ## [What to move out of Obsidian, and what to leave in it](https://commitcycle.com/insights/what-to-move-out-of-obsidian/)
  [A line you can apply per note — if being wrong about it would mislead somebody else, it has outgrown a personal vault. What moves, and where to.](https://commitcycle.com/insights/what-to-move-out-of-obsidian/)
- [![](https://commitcycle.com/og/insights/obsidian-ai-agent-knowledge-base-600w.webp)](https://commitcycle.com/insights/obsidian-ai-agent-knowledge-base/)
  ## [Your Obsidian vault cannot be your AI agents' knowledge base](https://commitcycle.com/insights/obsidian-ai-agent-knowledge-base/)
  [Obsidian is a thinking tool for one person. Agents need project knowledge that is shared, cited, and provably current — three things a vault cannot be.](https://commitcycle.com/insights/obsidian-ai-agent-knowledge-base/)