@etus/bhono-app 0.1.1

package/templates/base/.claude/skills/linear/scripts/status/list.ts

@@ -0,0 +1,31 @@
+import { client } from "../../lib/client.js";
+import { outputWithJq } from "../../lib/output.js";
+import { getTeamIdOrExit } from "../../lib/config.js";
+
+async function listStatuses() {
+	const teamId = getTeamIdOrExit(2);
+
+	const team = await client.team(teamId);
+
+	if (!team) {
+		console.error("Team not found");
+		process.exit(1);
+	}
+
+	const statesResponse = await team.states();
+
+	const statuses = statesResponse.nodes.map((state) => ({
+		id: state.id,
+		name: state.name,
+		type: state.type,
+		color: state.color,
+		position: state.position,
+	}));
+
+	outputWithJq({ statuses });
+}
+
+listStatuses().catch((error) => {
+	console.error("Error listing statuses:", error.message);
+	process.exit(1);
+});

package/templates/base/.claude/skills/linear/scripts/status/set-by-name.ts

@@ -0,0 +1,78 @@
+import { client } from "../../lib/client.js";
+import { outputWithJq } from "../../lib/output.js";
+import { getTeamIdOrExit } from "../../lib/config.js";
+
+/**
+ * Update issue status by status name (e.g., "Done", "In Progress")
+ *
+ * Usage:
+ *   npx tsx scripts/status/set-by-name.ts ABC-123 "Done" --json
+ *   npx tsx scripts/status/set-by-name.ts ABC-123 "In Progress" --json
+ *
+ * This avoids the need for jq chaining to find status IDs.
+ */
+async function setStatusByName() {
+	const issueId = process.argv[2];
+	const statusName = process.argv[3];
+
+	if (!issueId || !statusName) {
+		console.error("Error: Please provide issue ID and status name");
+		console.error(
+			"Usage: npx tsx scripts/status/set-by-name.ts <issueId> <statusName> [--json]"
+		);
+		console.error("Example: npx tsx scripts/status/set-by-name.ts ABC-123 \"Done\" --json");
+		console.error("\nCommon status names: Backlog, Todo, In Progress, In Review, Done, Canceled");
+		process.exit(1);
+	}
+
+	// Get team states
+	const teamId = getTeamIdOrExit(4); // Skip 4 args: node, script, issueId, statusName
+	const team = await client.team(teamId);
+
+	if (!team) {
+		console.error("Team not found");
+		process.exit(1);
+	}
+
+	const statesResponse = await team.states();
+
+	// Find status by name (case-insensitive)
+	const targetState = statesResponse.nodes.find(
+		(state) => state.name.toLowerCase() === statusName.toLowerCase()
+	);
+
+	if (!targetState) {
+		const availableStates = statesResponse.nodes.map((s) => s.name).join(", ");
+		console.error(`Error: Status "${statusName}" not found`);
+		console.error(`Available statuses: ${availableStates}`);
+		process.exit(1);
+	}
+
+	// Update the issue
+	const issuePayload = await client.updateIssue(issueId, {
+		stateId: targetState.id,
+	});
+
+	const issue = await issuePayload.issue;
+
+	if (!issue) {
+		console.error("Failed to update issue status");
+		process.exit(1);
+	}
+
+	const state = await issue.state;
+
+	outputWithJq({
+		id: issue.id,
+		identifier: issue.identifier,
+		title: issue.title,
+		status: state?.name || "Unknown",
+		statusId: state?.id,
+		updatedAt: issue.updatedAt,
+	});
+}
+
+setStatusByName().catch((error) => {
+	console.error("Error updating issue status:", error.message);
+	process.exit(1);
+});

package/templates/base/.claude/skills/linear/scripts/status/update.ts

@@ -0,0 +1,44 @@
+import { client } from "../../lib/client.js";
+import { outputWithJq } from "../../lib/output.js";
+
+async function updateIssueStatus() {
+	const issueId = process.argv[2];
+	const stateId = process.argv[3];
+
+	if (!issueId || !stateId) {
+		console.error("Error: Please provide issue ID and state ID");
+		console.error(
+			"Usage: npx tsx scripts/status/update.ts <issueId> <stateId>"
+		);
+		console.error(
+			"Tip: Use scripts/status/list.ts to see available states"
+		);
+		process.exit(1);
+	}
+
+	const issuePayload = await client.updateIssue(issueId, {
+		stateId,
+	});
+
+	const issue = await issuePayload.issue;
+
+	if (!issue) {
+		console.error("Failed to update issue status");
+		process.exit(1);
+	}
+
+	const state = await issue.state;
+
+	outputWithJq({
+		id: issue.id,
+		identifier: issue.identifier,
+		title: issue.title,
+		status: state?.name || "Unknown",
+		updatedAt: issue.updatedAt,
+	});
+}
+
+updateIssueStatus().catch((error) => {
+	console.error("Error updating issue status:", error.message);
+	process.exit(1);
+});

package/templates/base/.claude/skills/linear/scripts/users/list.ts

@@ -0,0 +1,59 @@
+import { client } from "../../lib/client.js";
+import { outputWithJq } from "../../lib/output.js";
+import { loadConfigIfExists } from "../../lib/config.js";
+
+async function listUsers() {
+	let teamId = process.argv[2];
+
+	// If no teamId provided, try to use default from config
+	if (!teamId) {
+		const config = loadConfigIfExists();
+		teamId = config?.defaults?.teamId;
+
+		if (teamId) {
+			console.error(`ℹ️  Using team from config: ${config.defaults.teamName}`);
+		}
+	}
+
+	if (teamId) {
+		// List users for a specific team
+		const team = await client.team(teamId);
+
+		if (!team) {
+			console.error("Team not found");
+			process.exit(1);
+		}
+
+		const membersResponse = await team.members();
+
+		const users = membersResponse.nodes.map((user) => ({
+			id: user.id,
+			name: user.name,
+			email: user.email,
+			displayName: user.displayName,
+			admin: user.admin,
+			active: user.active,
+		}));
+
+		outputWithJq({ users });
+	} else {
+		// List all users in the organization
+		const usersResponse = await client.users();
+
+		const users = usersResponse.nodes.map((user) => ({
+			id: user.id,
+			name: user.name,
+			email: user.email,
+			displayName: user.displayName,
+			admin: user.admin,
+			active: user.active,
+		}));
+
+		outputWithJq({ users });
+	}
+}
+
+listUsers().catch((error) => {
+	console.error("Error listing users:", error.message);
+	process.exit(1);
+});

package/templates/base/.claude/skills/linear/scripts/users/me.ts

@@ -0,0 +1,20 @@
+import { client } from "../../lib/client.js";
+import { outputWithJq } from "../../lib/output.js";
+
+async function getCurrentUser() {
+	const viewer = await client.viewer;
+
+	outputWithJq({
+		id: viewer.id,
+		name: viewer.name,
+		email: viewer.email,
+		displayName: viewer.displayName,
+		admin: viewer.admin,
+		createdAt: viewer.createdAt,
+	});
+}
+
+getCurrentUser().catch((error) => {
+	console.error("Error fetching current user:", error.message);
+	process.exit(1);
+});

package/templates/base/.claude/skills/linear/templates/README.md

@@ -0,0 +1,203 @@
+# Linear Issue Templates Guide
+
+This guide covers best practices for creating and using issue templates in Linear, both via the UI and the API.
+
+## Overview
+
+Templates in Linear:
+- Speed up issue creation with pre-filled fields
+- Ensure consistent information capture across teams
+- Enable filtering and reporting by template type
+- Work across Linear UI, Slack, Asks, and API
+
+## Template Types
+
+### 1. Standard Templates
+
+Pre-defined issue formats with:
+- Title prefix/format
+- Description (markdown with placeholder text)
+- Default labels, priority, project, assignee
+- Estimate and due date defaults
+
+### 2. Form Templates (Business/Enterprise)
+
+Structured forms with custom fields:
+- Text inputs, dropdowns, checkboxes
+- Required field validation
+- Issue property fields (priority, customer, labels)
+- Field descriptions and instructions
+
+## Creating Templates
+
+### Via Linear UI
+
+1. Navigate to **Settings** → **Team** → **Templates**
+2. Click **New Template**
+3. Configure:
+   - Template name
+   - Description with placeholder text
+   - Default properties (labels, priority, project)
+4. Save template
+
+### Via API
+
+```bash
+# Create issue from template
+npx tsx scripts/issues/create.ts \
+  --title "Bug: Login broken" \
+  --templateId "template-uuid" \
+  --json
+```
+
+The API's `IssueCreateInput` accepts:
+- `templateId` - UUID of the template to use
+- `useDefaultTemplate` - Boolean to use team's default template
+
+**Note:** Values provided in the input override template defaults.
+
+## Best Practices
+
+### 1. Naming Conventions
+
+Use clear, action-oriented titles:
+```
+✅ [Verb] [What] [Context]
+   "Fix broken scroll in mobile navbar"
+   "Add dark mode toggle to settings"
+
+❌ Vague titles
+   "Bug"
+   "Feature"
+```
+
+### 2. Structured Descriptions
+
+Include consistent sections:
+```markdown
+## Background
+Why are we doing this? What's the context?
+
+## Requirements
+- [ ] Requirement 1
+- [ ] Requirement 2
+
+## Acceptance Criteria
+What defines "done"?
+
+## Links
+- Design: [Figma link]
+- Spec: [Doc link]
+```
+
+### 3. Use Placeholder Text
+
+In Linear UI, format text as placeholder (select text → click **Aa** icon):
+```markdown
+## Steps to Reproduce
+<Describe the steps you took>
+
+## Expected Behavior
+<What should have happened>
+
+## Actual Behavior
+<What actually happened>
+```
+
+### 4. Set Appropriate Defaults
+
+Pre-fill fields that are always the same:
+- Bug reports → "bug" label, Triage status
+- Feature requests → "enhancement" label
+- Technical debt → "tech-debt" label, Low priority
+
+### 5. Keep Templates Minimal
+
+Only include fields that are truly necessary. Too many required fields = friction.
+
+## Template Examples
+
+See the following files for ready-to-use templates:
+
+| Template | File | Use Case |
+|----------|------|----------|
+| Bug Report | `bug-report.md` | User-reported bugs, QA findings |
+| Feature Request | `feature-request.md` | New features, enhancements |
+| Technical Debt | `tech-debt.md` | Refactoring, code cleanup |
+| Security Issue | `security-issue.md` | Vulnerabilities, security fixes |
+| Sprint Task | `sprint-task.md` | General sprint work items |
+
+## Filtering by Template
+
+Issues created from templates are filterable:
+```
+template:Bug Report
+template:Feature Request
+```
+
+Use Insights to analyze:
+- Bug reports vs feature requests ratio
+- Resolution time by template type
+- Template usage by team
+
+## Integration with Slack/Asks
+
+Templates can be used in:
+- **Slack**: Up to 5 templates available via `/linear` command
+- **Asks**: Form templates for external stakeholders
+- **Email**: Create issues from templates via intake email
+
+## API Reference
+
+### Query Templates
+
+```graphql
+query {
+  templates {
+    nodes {
+      id
+      name
+      description
+      type
+      team { id name }
+    }
+  }
+}
+```
+
+### Create Issue from Template
+
+```graphql
+mutation {
+  issueCreate(input: {
+    title: "Issue title"
+    teamId: "team-uuid"
+    templateId: "template-uuid"
+  }) {
+    success
+    issue { id identifier url }
+  }
+}
+```
+
+### Using Default Template
+
+```graphql
+mutation {
+  issueCreate(input: {
+    title: "Issue title"
+    teamId: "team-uuid"
+    useDefaultTemplate: true
+  }) {
+    success
+    issue { id identifier url }
+  }
+}
+```
+
+## Sources
+
+- [Linear Issue Templates Documentation](https://linear.app/docs/issue-templates)
+- [Linear Project Templates](https://linear.app/docs/project-templates)
+- [Linear Form Templates (Nov 2025)](https://linear.app/changelog/2025-11-20-form-templates)
+- [Linear API Documentation](https://linear.app/developers/graphql)

package/templates/base/.claude/skills/linear/templates/api-reference.md

@@ -0,0 +1,258 @@
+# Templates API Reference
+
+This document covers how to work with Linear templates programmatically via the API.
+
+## Creating Issues from Templates
+
+### Using templateId
+
+When creating an issue, you can specify a `templateId` to apply a template's defaults:
+
+```bash
+npx tsx scripts/issues/create.ts \
+  --title "Bug: Login broken" \
+  --templateId "template-uuid-here" \
+  --json
+```
+
+**Note:** Values provided in the input **override** template defaults. So if you specify `--priority 1` but the template has priority 3, the issue will have priority 1.
+
+### Using Default Template
+
+To use the team's default template:
+
+```graphql
+mutation {
+  issueCreate(input: {
+    title: "New issue"
+    teamId: "team-uuid"
+    useDefaultTemplate: true
+  }) {
+    success
+    issue { id identifier }
+  }
+}
+```
+
+## Querying Templates
+
+### List All Templates
+
+```graphql
+query {
+  templates {
+    nodes {
+      id
+      name
+      description
+      type
+      templateData
+      team {
+        id
+        name
+      }
+      creator {
+        id
+        name
+      }
+      createdAt
+      updatedAt
+    }
+  }
+}
+```
+
+### Get Team-Specific Templates
+
+```graphql
+query {
+  team(id: "team-uuid") {
+    templates {
+      nodes {
+        id
+        name
+        description
+      }
+    }
+    defaultTemplateForMembers {
+      id
+      name
+    }
+    defaultTemplateForNonMembers {
+      id
+      name
+    }
+  }
+}
+```
+
+### Get Single Template
+
+```graphql
+query {
+  template(id: "template-uuid") {
+    id
+    name
+    description
+    type
+    templateData
+    team {
+      id
+      name
+    }
+  }
+}
+```
+
+## Template Types
+
+| Type | Description |
+|------|-------------|
+| `issue` | Standard issue template |
+| `project` | Project template with milestones |
+
+## Template Fields
+
+The `templateData` field contains a JSON object with the template's default values:
+
+```json
+{
+  "title": "Bug: ",
+  "description": "## Summary\n\n## Steps to Reproduce\n\n## Expected Behavior\n\n## Actual Behavior",
+  "priority": 2,
+  "labelIds": ["label-uuid-1", "label-uuid-2"],
+  "stateId": "state-uuid",
+  "assigneeId": "user-uuid",
+  "projectId": "project-uuid",
+  "estimate": 3
+}
+```
+
+## Creating Templates via API
+
+### Create Issue Template
+
+```graphql
+mutation {
+  templateCreate(input: {
+    name: "Bug Report"
+    type: issue
+    teamId: "team-uuid"
+    description: "Template for bug reports"
+    templateData: {
+      description: "## Summary\n\n## Steps to Reproduce\n\n"
+      priority: 2
+      labelIds: ["bug-label-uuid"]
+    }
+  }) {
+    success
+    template {
+      id
+      name
+    }
+  }
+}
+```
+
+### Update Template
+
+```graphql
+mutation {
+  templateUpdate(
+    id: "template-uuid"
+    input: {
+      name: "Updated Bug Report"
+      templateData: {
+        priority: 1
+      }
+    }
+  ) {
+    success
+    template {
+      id
+      name
+    }
+  }
+}
+```
+
+### Delete Template
+
+```graphql
+mutation {
+  templateDelete(id: "template-uuid") {
+    success
+  }
+}
+```
+
+## Workflow: Get Template ID for Issue Creation
+
+```bash
+# 1. List templates to find the ID
+TEMPLATES=$(npx tsx scripts/list-teams.ts --json)
+
+# Or query directly via GraphQL
+curl -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "query": "{ templates { nodes { id name team { key } } } }"
+  }' | jq '.data.templates.nodes[] | select(.name == "Bug Report")'
+
+# 2. Create issue using template ID
+npx tsx scripts/issues/create.ts \
+  --title "Bug: Specific issue" \
+  --templateId "found-template-uuid" \
+  --json
+```
+
+## Template + URL Creation (linear.new)
+
+Create pre-filled issues via URL:
+
+```
+https://linear.app/workspace/team/KEY/new?template=template-uuid
+https://linear.app/workspace/team/KEY/new?template=template-uuid&title=Override+Title
+```
+
+URL parameters **override** template values:
+- `title` - Issue title
+- `description` - Issue description
+- `priority` - Priority (0-4)
+- `labelIds` - Comma-separated label UUIDs
+- `assigneeId` - Assignee UUID
+- `projectId` - Project UUID
+
+## Best Practices
+
+1. **Template Inheritance**: Values you provide always override template defaults
+
+2. **Team vs Workspace Templates**:
+   - Team templates: Only available to that team
+   - Workspace templates: Available to all teams (`teamId: null`)
+
+3. **Default Templates**: Teams can set default templates for:
+   - Members (internal issue creation)
+   - Non-members (external/Asks issue creation)
+
+4. **Template Versioning**: Templates don't version - changes apply immediately
+
+5. **Finding Template IDs**:
+   - Use GraphQL explorer: https://studio.apollographql.com/public/Linear-API
+   - Query templates endpoint
+   - Check URL when editing template in UI
+
+## Error Handling
+
+| Error | Cause | Solution |
+|-------|-------|----------|
+| `Template not found` | Invalid templateId | Query templates to get valid IDs |
+| `Permission denied` | Template belongs to different team | Use team-specific template or workspace template |
+| `Invalid template type` | Using project template for issue | Check template type field |
+
+## Sources
+
+- [Linear API Documentation](https://linear.app/developers/graphql)
+- [Linear GraphQL Schema](https://studio.apollographql.com/public/Linear-API/schema/reference)
+- [Create issues using linear.new](https://linear.app/developers/create-issues-using-linear-new)