ai-context-bridge
CLAUDE.md4 starsChanged 2 months agoApache-2.0View on GitHub
See ARCHITECTURE.md for the project overview, dev setup, architecture, and contribution guide — that file is the source of truth; this one just points to it so Claude Code loads it automatically each session. For cutting a release, this repo has a release-extension skill under .claude/skills/ — the full pipeline (readiness gate → version/merge → docs → changelog → tag → build+submit → post-release), not something to improvise from scratch each time.
In this repository2 other files it gives its agents.
- site/llms.txtllms.txt
- release-extensionSkill
The file
Files
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
See ARCHITECTURE.md for the project overview, dev setup, architecture, and contribution guide — that file is the source of truth; this one just points to it so Claude Code loads it automatically each session.
For cutting a release, this repo has a release-extension skill under .claude/skills/ — the full pipeline (readiness gate → version/merge → docs → changelog → tag → build+submit → post-release), not something to improvise from scratch each time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.