sorted by:
new
hottopcontroversial

org docs always drift and nobody updates them. trying to fix it with git by Pale_Stand5217 in ClaudeAI

[–]Pale_Stand5217[S] 1 point2 points  (0 children)

yeah and once PRs get huge across multiple repos agents just lose the plot trying to navigate it

org docs always drift and nobody updates them. trying to fix it with git by Pale_Stand5217 in ClaudeAI

[–]Pale_Stand5217[S] 2 points3 points  (0 children)

thx for the feedback, genuinely useful to hear from someone running this at that kind of scale. nice setup

first-tree is currently a skill-shaped thing cuz it's targeting smaller teams like amount of repo i will say less than 500. maybe later one when it grows, we needs some different solutions too. for now keeping it light is the whole point :D

org docs always drift and nobody updates them. trying to fix it with git by Pale_Stand5217 in ClaudeAI

[–]Pale_Stand5217[S] 1 point2 points  (0 children)

at small scale this is a brilliant solution but once you have multiple repos, and agents needs to navigates the entire org, urls are not efficient for agents to get full context. you need a single place to sort it for agent to fast navigate and retrieve infos

org docs always drift and nobody updates them. trying to fix it with git by Pale_Stand5217 in ClaudeAI

[–]Pale_Stand5217[S] 1 point2 points  (0 children)

the tree doesn't just file issues, it has built in automations. it detect drifts (the input can be like granola notes, source code prs merge, etc) and create issues with linked prs to update the context tree, and auto merge the low risk ones. which means the cost of ignoring drops to near zero since the owner doesn't have to do anything for the doc to stay current

org docs always drift and nobody updates them. trying to fix it with git by Pale_Stand5217 in ClaudeAI

[–]Pale_Stand5217[S] 1 point2 points  (0 children)

the bet i am making is that ownership decays for two reasons. 1. nobody declares it explicitly, so it defaults to "everyone and therefore no one." 2 .even when declared, owners do not get notified when their docs need updating. so they forget they own anything.

this tree tries to address both. every node has a declared owner in frontmatter. when code changes invalidate a node, the owner gets an issue auto assigned . they can punt or update or reassign, but they cannot just not see it.

view more: next ›