crow-create-ticket

Crow Create Ticket

Create a new ticket (GitHub issue via gh, GitLab issue via glab, or Jira work item via the jira MCP server) for a repo/project in the current Crow workspace, assigned to the invoking user and labeled crow:auto. For GitHub/GitLab, Crow's auto-pickup queue then implements it. (Jira's auto-pickup isn't wired — the label is for parity/board visibility — but the work item is created with an assignee in one step, which acli could never do; CROW-528.)

Important: Sandbox Bypass

All gh, glab, and git commands require dangerouslyDisableSandbox: true because they communicate over the network (TLS) or read outside the sandbox-allowed directories. They will fail with TLS certificate errors otherwise.

Arguments

• $ARGUMENTS — the ticket title (required) and an optional body.
  • The first quoted string is the title.
  • Any remaining text (including multiple lines) is the body.
  • If no title can be determined, ask the user for one before proceeding.

Examples:

/crow-create-ticket "Fix tab URL hash routing"
/crow-create-ticket "Add JWT validation" The /auth endpoint should reject expired tokens.

Activation

This skill activates when:

• User invokes /crow-create-ticket command
• User asks to "create a ticket", "file an issue", or "open an issue" in Crow

Configuration

Configuration is at {devRoot}/.claude/config.json (managed by the Crow app), the same file used by /crow-workspace. It maps each workspace to a provider/cli/host:

{
  "devRoot": "/Users/name/Dev",
  "workspaces": {
    "Corveil": { "provider": "github", "cli": "gh" },
    "MyGitLab": { "provider": "gitlab", "cli": "glab", "host": "gitlab.example.com" }
  },
  "defaults": { "provider": "github", "cli": "gh" }
}

Provider Detection

Workspace taskProvider	Tool	Notes
github (or unset)	gh	—
gitlab	glab	workspace host
jira	jira MCP	project jiraProjectKey