crosslink-guide

Documents the crosslink CLI for issue tracking, sessions, locks, swarms, and knowledge pages.

1.4k|335|Updated Jun 10, 2014
One-click install
npx skills add https://github.com/openwpm/OpenWPM --skill crosslink-guide-openwpm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crosslink-guide
Source: https://github.com/openwpm/OpenWPM/tree/main/.claude/skills/crosslink-guide
Command: npx skills add https://github.com/openwpm/OpenWPM --skill crosslink-guide-openwpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted development sessions lose context between runs, collide on shared issues, and accidentally pollute CHANGELOG files when closing issues. This Skill provides the full crosslink CLI reference plus the undocumented hook behaviors so agents can track work, coordinate with other agents, and hand off sessions cleanly. ## Core Features & Use Cases - Issue and session lifecycle: Create, query, comment on, and close issues with typed comments, labels, priorities, and dependencies, paired with session start/work/end handoff notes. - Hook footgun awareness: Explains the auto-CHANGELOG entry on issue close, the --no-changelog escape hatch, label-based routing, and why session work fails without an active session. - Multi-agent coordination: Covers locks, kickoff agent launching, swarm phases and review pipelines, container execution, agent identity, and trust signing. - Use Case: An agent starting work in a repo with a .crosslink directory runs session start, claims an issue with crosslink quick, documents decisions as typed comments, and closes the issue with --no-changelog when the work is meta-only. ## Quick Start Ask the agent to start a crosslink session, pick an open issue to work on, and end the session with handoff notes for the next run.

Frequently Asked Questions about crosslink-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close a crosslink issue without adding a CHANGELOG entry?

Pass the --no-changelog flag to crosslink issue close, for example crosslink issue close 643 --no-changelog. Closing an issue normally triggers a hook that appends a line to CHANGELOG.md under Changed or Fixed, which pollutes release notes for meta-work.

Why does crosslink session work fail with no active session?

The session work command requires an active session, so run crosslink session start first and then crosslink session work <id>. The same applies to the --work flag on crosslink quick, which is silently ignored without a session.

How do crosslink issue locks work for multi-agent coordination?

Crosslink uses optimistic locking so agents do not collide on the same issue. crosslink quick and session work auto-claim locks, issue close releases them, and locks list, check, claim, release, and steal manage them manually.

What is the difference between crosslink issue IDs like #42 and L3?

A positive numeric ID like 42 is hub-synced and shared across clones, while an L-prefixed ID like L3 is local-only and not yet pushed to the hub branch. Both formats work interchangeably in all commands.

When should I use crosslink swarm versus kickoff?

Use kickoff to launch a single agent in a worktree for one issue, and swarm for multi-agent coordination across phases with gates, checkpoints, review pipelines, and merges. Swarm initializes from a design document and tracks budget and progress.