bridgelisted
Install: claude install-skill serdardb/context-bridge
The user wants to hand this session off to another coding agent via context-bridge.
Target agent: $ARGUMENTS
Follow these steps exactly:
1. If no target was given, ask which agent to hand off to and stop until they
answer. Otherwise take the target as written.
2. Write a SUMMARY of this conversation for the agent taking over, covering only
what happened since the last bridge point.
The bridge already carries the transcript, the git changes and a record of
every command that ran. What it cannot carry is which of that mattered, and
you are the only thing that knows. So do not list what happened; say what it
means.
Cover what was decided and why, what was tried and rejected, what is in
flight, and what is unresolved. Say what the next agent should verify first.
Where you are not certain, say so rather than writing it as settled: a summary
that sounds equally sure of everything is worse than one that marks its own
soft spots, because the reader cannot tell which parts to check.
Length is yours to judge. There is no item count and no sentence limit. The
only limit is a byte budget, and the command will tell you the number if you
go past it. Do not summarise the whole project, only what happened since the
bridge brought you here; if nothing of substance happened, say that in a line.
3. Compose two short notes as well:
- DECISIONS: the concrete decisions made, including rejected approaches and why.
- NEXT: the current objecti