A team inside your repository

Check the repository for contradictions and stale docs, request changes your AI team makes, see why every version exists, and who's working right now.

A GitHub repository is files that wait for someone to change them. A GitPanda repository has a team inside it: AI employees in rooms who keep it true, make the changes you ask for, and leave a trail of why, not just who.

Command	What happens
`gitpanda check`	Finds contradictions, stale and empty docs, broken links, and rooms with nothing written down
`gitpanda check --fix`	Hands each issue to the room that owns it
`gitpanda request <file> "…"`	The room that owns the document makes the change, as a new version
`gitpanda request <room> "…"`	The room writes something new
`gitpanda why <file>`	Every version, who made it, and the goal and task behind it
`gitpanda now`	Who's working on what, right now

check: keep it true#

gitpanda check

  🐼  Repository health  76/100  42 documents checked

  ● ⚔️  Contradiction  The launch plan says tees are $25; the price list says $28.
       marketing/docs/launch-plan.md  ·  sales/docs/price-list.md
       → The price list was updated last week, so the launch plan is probably out of date.

  ● 🔗 Broken link  Links to price-list.md, which doesn't exist.
       marketing/docs/faq.md
       → Point the link at the right document, or remove it.

  ● 🕸️  Stale  Not updated in 140 days.
       operations/docs/returns.md
       → Check it's still right, and update or retire it.

Issue	Means
⚔️ Contradiction	Two documents disagree on a fact: a price, a date, a name, a policy. Found by AI.
🔗 Broken link	A link to a document that isn't there.
🕸️ Stale	Not updated in over 90 days (more serious after 180).
📄 Almost empty	A title and little else.
📭 No documents	A room with nothing written down.

The score starts at 100 and drops for each issue, most for contradictions.

--fix: hand it to the team#

gitpanda check --fix          # high and medium issues
gitpanda check --fix --all    # everything

Each issue becomes a goal for the room that owns the file: Marketing's documents go to Marketing's lead, company-wide ones to the Coordinator. They fix it and save a new version. Follow along with gitpanda goals, then gitpanda get to pull the fixes.

On the web: the repository's 🩺 Health tab runs the same check. Tick the issues and click Hand them to the team.

request: changes your team makes#

gitpanda request marketing/docs/launch-plan.md "Add this quarter's numbers and cut it to one page"
gitpanda request marketing "Write up how we run a launch, step by step"
gitpanda request sales/docs/price-list.md "Add the new hoodies" --watch

Like opening an issue, except someone actually does it:

The request goes to the room that owns the document (its folder).
Its lead reads the document and makes the change.
The result is saved in place, as a new version, with the task as its message.
Anything sensitive still waits for your approval, as always.

Option
`--watch`	Watch the work live.
`--auto`	Don't stop for approvals (needs the approve scope).

On the web: ✋ Request a change on any document.

When it's done: gitpanda get pulls the new version, and gitpanda why <file> shows where it came from.

why: blame that explains#

gitpanda why marketing/docs/launch-plan.md

  🐼  Launch plan  marketing/docs/launch-plan.md · version 3

  ● T-41 Add this quarter's numbers  v3 · 2 hours ago
      🐼 Sol, Head of Marketing (AI employee)
      because G-12 Plan the spring sale › T-41 Add this quarter's numbers
      Added Q3 revenue by channel and cut the plan to one page.

  ● Lead with the price  v2 · yesterday
      👤 you@acme.com

  ● Add Launch plan  v1 · last week
      🐼 Sol, Head of Marketing (AI employee)
      because G-9 Prepare the launch › T-30 Draft the launch plan

git blame tells you who touched a line. gitpanda why tells you why the document changed: the goal it served, the task that did it, and what the employee said it did. On the web: 🕘 Why on any document.

now: who's working on what#

gitpanda now

  🐼  Working now

    ● Sol (Marketing) is writing "Spring sale plan"  · G-12
    ● Rui (Operations) is on T-44 Restock the hoodies

gitpanda status shows the same thing under your changes, and the repository's web page has a live strip at the top, so you know when someone's about to change what you're reading.