Skip to main content
ClaudeWave
Skill58 estrellas del repoactualizado 2mo ago

jira-management

Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/monkilabs/opencastle /tmp/jira-management && cp -r /tmp/jira-management/src/orchestrator/plugins/jira ~/.claude/skills/jira-management
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->

# Task Management with Jira

For project-specific project keys, workflow state IDs, and board configuration, see [tracker-config.md](../../.opencastle/project/tracker-config.md).

## MCP Tool Examples

```json
// Search issues
{ "jql": "project = PROJ AND status = 'In Progress' ORDER BY priority DESC" }

// Create issue
{ "project": "PROJ", "summary": "[UI] Build PriceRangeFilter", "type": "Task", "description": "Objective: ...\nFiles: ...\nAC: ..." }

// Transition issue
{ "issueKey": "PROJ-42", "status": "In Progress" }
```

## Discovered Issues

Check Jira first; if untracked, create a `[Bug]` issue in Backlog with symptoms, repro steps, and affected files.

## Issue Naming

Use `[Area] Short description` format in the Summary field:

```
[Schema] Add priceRange field to place type
[DB] Add price_range column and migration
[Query] Update query with priceRange filter
[UI] Build PriceRangeFilter component
[Page] Integrate price filter into /places
[Test] E2E test price range filtering
[Docs] Update data model documentation
```


## Status Workflow

```
Backlog → To Do → In Progress → In Review → Done
```

### Transition Rules

- Agent (via MCP): `To Do → In Progress` on start; `In Progress → Done` on verified completion.
- Automation: PR events auto-update status when GitHub/Jira integration is configured.
- Link via Jira key in branch/PR title (e.g., `PROJ-123`).

## Issue Descriptions

Every issue must include: **Objective** (one sentence), **Files (partition)** (paths this agent may modify), **Acceptance Criteria** (verifiable checklist), **Dependencies** (issue keys).

Group related issues under a Jira Epic; use components or labels for domain grouping.

## Session Workflow

1. Search the board (JQL) for existing in-progress work.
2. Decompose the feature into issues; create all in Jira — verify each returns a valid issue key.
3. Link dependencies between issues.
4. Delegate: move issue to **In Progress** before starting; move to **Done** after verified.
5. If creation/transition fails: retry once; check project key and workflow state IDs in [tracker-config.md](../../.opencastle/project/tracker-config.md).
6. On resume: search by status (In Progress, To Do), read descriptions, continue.
7. On completion: verify all Epic issues are Done, run build/lint/test, close the Epic.

## JQL Quick Reference

Common queries for agent workflows:

```jql
project = PROJ AND status = "In Progress" ORDER BY priority DESC
project = PROJ AND status = "To Do" ORDER BY priority DESC
project = PROJ AND type = Bug AND status != Done ORDER BY priority DESC
project = PROJ AND sprint in openSprints() ORDER BY priority DESC
project = PROJ AND priority = Highest AND status != Done
```
astro-frameworkSkill

Creates pages/layouts, defines content collections, configures hydration directives, and wires integrations. Use when adding or modifying Astro pages, layouts, components, or content collections. Trigger terms: Astro, content collection, client:load, client:visible, astro:content

browser-testingSkill

Drive real browsers via Chrome DevTools MCP: navigate pages, capture snapshots, run responsive checks, and collect console/perf traces. Use when the user mentions: 'validate UI change in Chrome', 'capture a screenshot', 'run responsive checks', or 'collect console logs'. Trigger terms: browser testing, DevTools, console logs, screenshot, responsive testing

cloudflare-platformSkill

Creates and deploys Cloudflare Workers, configures wrangler.toml bindings, sets up KV/D1/R2 storage and Durable Objects, manages Pages deployments, and implements edge function patterns. Use when building or deploying Cloudflare Workers, setting up Pages, working with KV/D1/R2 storage, configuring wrangler.toml, or deploying edge applications.

contentful-cmsSkill

Creates Contentful content types, queries entries via GraphQL/REST, runs CLI migrations, and manages assets and locales. Use when building or modifying Contentful content models, writing queries, or migrating content.

convex-databaseSkill

Convex reactive database patterns, schema design, real-time queries, mutations, actions, authentication, migrations, performance optimization, and component creation. Use when designing Convex schemas, writing queries/mutations, managing the Convex backend, setting up auth, migrating data, optimizing performance, or building Convex components.

coolify-deploymentSkill

Deploys applications, databases, and services on self-hosted Coolify instances, manages environments and env vars, runs infrastructure diagnostics, and performs batch operations. Use when deploying apps to Coolify, managing Coolify servers, debugging deployment issues, setting up databases, or managing Coolify infrastructure.

cypress-testingSkill

Writes Cypress E2E/component tests, configures `cy.intercept()` and `cy.session()`, authors custom commands, and wires CI artifacts. Use when creating E2E specs, component tests, or CI test pipelines. Trigger terms: cypress, e2e, component test, cy.intercept, cy.session

drizzle-ormSkill

Drizzle ORM schema definition, type-safe queries, relational queries, CRUD operations, transactions, migrations with drizzle-kit, and database setup for PostgreSQL, MySQL, and SQLite. Use when defining database schemas, writing queries or joins, managing migrations, setting up a new Drizzle project, or working with drizzle-kit.