init

init

You help the user get set up to use the rfe plugin. Work through the three phases below in order, stopping if any required step fails.

---

Phase 1: Check Prerequisites

acli

Run:

acli --version

• If it succeeds → note the version and continue.
• If it fails (command not found) → stop and tell the user:

  "acli is not installed. Install the Atlassian CLI from https://developer.atlassian.com/cloud/acli/ and re-run /rfe:init."

---

Phase 2: Configure JIRA Access

Check whether JIRA_URL, JIRA_API_TOKEN, and JIRA_USER are set:

echo "JIRA_URL=${JIRA_URL:+set}"
echo "JIRA_API_TOKEN=${JIRA_API_TOKEN:+set}"
echo "JIRA_USER=${JIRA_USER:+set}"

• If all three are set → skip to Phase 3.
• If any are missing → guide the user through setup.

Collecting credentials

Tell the user:

To use the rfe plugin you need the Jira base URL, an API token, and your email address.

Steps:

1. Your JIRA_URL is the base URL of your Jira instance (e.g. https://redhat.atlassian.net)
2. Go to https://id.atlassian.com/manage-profile/security/api-tokens
3. Click Create API token, give it a name (e.g. claude-code)
4. Copy the token — you won't see it again
5. Your JIRA_USER is the email address you use to log in to Jira

Then use AskUserQuestion to collect the Jira URL (if missing), token value (if missing), and email (if missing).

Once collected:

1. Determine the user's shell profile file. Check in order:

   • ~/.zshrc (if $SHELL contains zsh or if the file exists)
   • ~/.bashrc (fallback)

2. Append the exports to the profile file:

echo 'export JIRA_URL="<URL>"' >> ~/.zshrc
echo 'export JIRA_API_TOKEN="<TOKEN>"' >> ~/.zshrc
echo 'export JIRA_USER="<EMAIL>"' >> ~/.zshrc

3. Export them in the current session:

export JIRA_URL="<URL>"
export JIRA_API_TOKEN="<TOKEN>"
export JIRA_USER="<EMAIL>"

4. Tell the user:

Credentials saved to ~/.zshrc. They will be available automatically in new shell sessions. For the current session they have already been exported.

---

Phase 3: Verify Access

Run a minimal search using acli to confirm the token works and JIRA is reachable:

acli jira workitem search --jql 'project = RFE AND issuetype = "Feature Request"' --limit 1 --json

• If it returns one issue → access is confirmed.
• If it returns an authentication error (401/403) → tell the user:

  "The JIRA API token was rejected. Check that it hasn't expired and that it was copied correctly. Re-run /rfe:init to enter a new token."

• If it returns a network error → tell the user:

  "Could not reach $JIRA_URL. Check your network connection and try again."

---

Phase 4: Report Summary

Print a summary table:

rfe setup check
───────────────────────────────────
  acli             ✓  x.y.z
  JIRA_URL         ✓  configured
  JIRA_API_TOKEN   ✓  configured
  JIRA_USER        ✓  configured
  JIRA access      ✓  acli query succeeded
───────────────────────────────────
All checks passed. You're ready to use the rfe plugin.

Next step: /rfe:triage

If any check failed, replace the corresponding line with ✗ and the failure reason, and omit the "Next step" line.