crosslink-guide

Document crosslink CLI subcommands and undocumented behavioral footguns.

6|3|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dollspace-gay/crosslink --skill crosslink-guide-dollspace-gay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crosslink-guide
Source: https://github.com/dollspace-gay/crosslink/tree/main/crosslink/resources/claude/skills/crosslink-guide
Command: npx skills add https://github.com/dollspace-gay/crosslink --skill crosslink-guide-dollspace-gay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI coding agents lose persistent work context between sessions, hit undocumented crosslink CLI behavioral footguns (like accidental CHANGELOG pollution or failed session commands), and waste time reorienting or fixing avoidable workflow errors.

Core Features & Use Cases

  • Full CLI Reference: Covers every crosslink subcommand for issue tracking, session management, locks, swarms, kickoff, knowledge bases, and more.
  • Hidden Footgun Documentation: Exposes undocumented hook behaviors (auto-CHANGELOG entries on issue close, label-based CHANGELOG routing, session start requirements for work commands) that are not present in standard --help output.
  • Use Case: When an agent needs to close a meta-issue (like a skill edit or settings tweak) without adding an entry to the project CHANGELOG, or start a new session and retrieve the previous handoff notes to resume work seamlessly.

Quick Start

Use the crosslink-guide skill to look up the correct crosslink command for closing an issue without adding a CHANGELOG entry, or to start a new session and retrieve the previous handoff notes.

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 an entry to the project CHANGELOG?

To close a crosslink issue without adding a CHANGELOG entry, use the --no-changelog flag. This prevents auto-CHANGELOG entry generation on issue close, avoiding release note pollution for meta-issues like settings tweaks or skill edits.

Why do crosslink session commands fail when I try to start work without a session?

Crosslink session commands fail because work commands have session start requirements. You must start a new session first to properly initialize the context and retrieve the previous handoff notes to resume work seamlessly.

How does label-based CHANGELOG routing work in crosslink issue tracking?

Label-based CHANGELOG routing in crosslink automatically directs issue close entries to specific CHANGELOG sections based on assigned labels. This hidden hook behavior is not present in standard --help output but affects release note organization.

Can I use crosslink CLI for multi-agent swarm workflows and lock coordination?

Yes, crosslink CLI supports swarm multi-agent workflows, lock coordination, kickoff launches, and knowledge base operations. The full command surface covers issue tracking, session management, and locks across all crosslink-enabled repositories.

What undocumented crosslink hook behaviors should AI coding agents watch out for?

Undocumented crosslink hook behaviors include auto-CHANGELOG entry generation on issue close, label-based CHANGELOG routing, and session start requirements for work commands. These footguns are not visible in standard --help output and can cause workflow errors.

How do I retrieve previous handoff notes when starting a new crosslink session?

To retrieve previous handoff notes when starting a new crosslink session, use the session start command. This initializes the session context and retrieves prior handoff notes, allowing AI coding agents to resume work seamlessly without losing persistent context.