chore: remove PII from create-issue skill

[jamesc]

Summary

• Replace hardcoded jamesc.000@gmail.com with --assignee me in the create-issue skill
• The Linear CLI resolves me to the authenticated user, so behavior is unchanged

Motivation

PII audit flagged the personal email address (3 occurrences). Skills may be shared or made public — no reason to hardcode an email when --assignee me works.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated Linear issue creation instructions to support assigning issues to the current user via a placeholder flag, replacing the previous fixed assignee configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated Linear issue creation instructions to replace a hardcoded assignee email (jamesc.000@gmail.com) with a placeholder flag (--assignee me), allowing issues to be assigned to the current user instead of a fixed person.

Changes

Cohort / File(s)	Summary
Issue Creation Instructions skills/create-issue/SKILL.md	Changed assignee requirement from fixed email (James Casey) to --assignee me placeholder for dynamic user assignment in both instructions and rules sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing PII (a personal email address) from the create-issue skill documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-pii

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

skills/create-issue/SKILL.md (1)

19-19: Required assignee rule is not reflected in the CLI example.

You made assignee mandatory (--assignee me), but the “Creating via CLI” example (Lines 120-124) still omits --assignee me. That makes the workflow internally inconsistent and easy to follow incorrectly.

Suggested doc fix

 streamlinear-cli create \
   --team BT \
+  --assignee me \
   --title "Implement feature X" \
   --body "Context:\n...\n\nAcceptance Criteria:\n- [ ] ..." \
   --priority 3

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@skills/create-issue/SKILL.md` at line 19, The CLI example under "Creating via
CLI" does not include the required assignee flag declared in the table (`|
**Assignee** | `--assignee me` (current user) |`); update the example command to
include `--assignee me` and add a brief note in that example indicating that
assignee is required (or show the required flag in the example invocation) so
the documentation is consistent with the rule.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@skills/create-issue/SKILL.md`:
- Line 19: The CLI example under "Creating via CLI" does not include the
required assignee flag declared in the table (`| **Assignee** | `--assignee me`
(current user) |`); update the example command to include `--assignee me` and
add a brief note in that example indicating that assignee is required (or show
the required flag in the example invocation) so the documentation is consistent
with the rule.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a1e264be-7d3f-4c7c-9a9f-a78e456f4ed9

📥 Commits

Reviewing files that changed from the base of the PR and between a0abf87 and 11263e6.

📒 Files selected for processing (1)

• skills/create-issue/SKILL.md