zhongwei/gh-greyhaven-ai-claude-code-config-grey-haven-plugins-linear

Files

Zhongwei Li 742559fa58 Initial commit

2025-11-29 18:29:20 +08:00

9.3 KiB

Raw Blame History

name, description

name	description
grey-haven-linear-workflow	Grey Haven's Linear issue workflow - creating well-documented issues, proper branch naming from issue IDs, commit message integration, PR linking, and status management. Use when creating issues, starting work, or managing project workflow.

Grey Haven Linear Workflow

Follow Grey Haven Studio's workflow for Linear issue management, Git branching, and pull request integration.

Linear Issue Management

Issue Creation Guidelines

Always create Linear issues BEFORE starting work to track progress and context.

Issue Title Format: Specific, actionable statements

[OK] Good titles:
- Add magic link authentication
- Fix race condition in user repository
- Migrate organizations table to multi-tenant

[X] Bad titles (too vague):
- Auth improvements
- Fix bug
- Update dependencies

Issue Templates

Feature Issue Structure:

Title: Add magic link authentication

## Description
[What you're building]

## Motivation
[Why this is needed - user pain points, business value]

## Acceptance Criteria
- [ ] Specific, testable criteria
- [ ] Include multi-tenant isolation requirements
- [ ] Target >80% test coverage

## Technical Notes
- Tech stack references (better-auth, TanStack, etc.)
- Doppler environment variables needed
- Database schema changes (snake_case fields)

## Related Issues
- Blocks: GREY-XXX
- Related: GREY-YYY

Labels: feature, [component], [priority]
Estimate: X points

Bug Issue Structure:

Title: Fix race condition in user repository

## Description
[What's broken]

## Steps to Reproduce
1. [Step-by-step]
2. [With specific inputs]
3. [Expected vs actual]

## Impact
- Frequency: X% of requests
- User experience impact
- Data corruption risk

## Proposed Solution
[How to fix it]

## Environment
- Backend: cvi-backend-template
- Database: PostgreSQL with RLS
- Doppler config: production

Labels: bug, [component], [priority]
Priority: [critical/high-priority/normal/low-priority]

Labels

Type Labels: feature, bug, chore, docs, refactor, performance

Component Labels: frontend, backend, database, auth, multi-tenant, testing

Priority Labels: critical, high-priority, low-priority

Story Point Estimates

Use Fibonacci sequence:

1 point: < 1 hour (config change, simple fix)
2 points: 1-2 hours (small feature, simple bug)
3 points: Half day (moderate feature)
5 points: 1 day (complex feature, migration)
8 points: 2-3 days (large feature, major refactor)
13 points: 1 week (should be broken down into smaller issues)

Git Branching Strategy

Branch Naming Convention

Format: <issue-id>-<type>-<short-description>

# Examples
GREY-234-feat-magic-link-auth
GREY-456-fix-user-race-condition
GREY-890-migrate-add-tenant-id
GREY-123-chore-update-dependencies
GREY-789-docs-update-api-guide

Creating Branches from Linear Issues

# Always branch from latest main!
git checkout main
git pull origin main
git checkout -b GREY-234-feat-magic-link-auth

Branch Protection Rules

Main branch protection:

✅ Require pull request before merging
✅ Require 1 approval
✅ Require status checks to pass
✅ Require branches to be up to date
✅ Require linear history (squash merges)
❌ Do NOT allow force pushes
❌ Do NOT allow deletions

Commit Message Integration

Format with Linear

<type>(<scope>): <subject>

[optional body]

[Linear issue reference]

Examples:

# Feature commit
feat(auth): add magic link authentication

Implement magic link provider using better-auth with email
verification via Resend.

- Single-use tokens with 15 minute expiry
- Tenant isolation via RLS policies
- Server functions for sending/verifying links

Closes GREY-234

# Bug fix commit
fix(repositories): prevent race condition in user creation

Add database-level unique constraint and proper IntegrityError
handling in UserRepository.

Fixes GREY-456

# Migration commit
feat(db): add tenant_id to organizations table

Add tenant_id column and RLS policies for multi-tenant isolation.
Backfill from service_id column.

Related to GREY-890

Linear Keywords

Use these keywords to automatically update Linear issues:

Closes GREY-123: Marks issue as Done when PR merges
Fixes GREY-123: Same as Closes (for bugs)
Related to GREY-123: Links issue without closing
Blocks GREY-123: Indicates dependency
Blocked by GREY-123: Indicates blocker

Pull Request Integration

PR Title Format

Include Linear ID at the end:

<type>(<scope>): <description> [GREY-123]