From jira
Bootstrap jira plugin environment - sets up venv, installs dependencies, validates setup
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:setup-plugin-envThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill handles the bootstrap process for jira plugin commands.
This skill handles the bootstrap process for jira plugin commands.
Ensures the Python virtual environment is created and dependencies are installed.
The plugin root directory is resolved by the UserPromptSubmit hook (context-hook.py),
which injects <jira-context> into the session. This skill only needs to handle
venv setup.
ALWAYS run this bootstrap FIRST before doing anything else in jira commands.
Extract PLUGIN_ROOT from the <jira-context> system reminder injected by the
UserPromptSubmit hook. Use the value from <plugin-root>.
If <jira-context> is not present, the hook may not have fired. Instruct the user
to verify the plugin is installed correctly.
Execute the plugin's environment setup script:
if [ ! -f "$PLUGIN_ROOT/scripts/setup_env.sh" ]; then
echo "✗ setup_env.sh not found in plugin directory" >&2
exit 1
fi
# Run setup script
bash "$PLUGIN_ROOT/scripts/setup_env.sh"
Check that the environment is ready:
VENV_PATH=".claude/jira/venv"
if [ ! -d "$VENV_PATH" ]; then
echo "✗ Virtual environment not created" >&2
exit 1
fi
# Check if Python dependencies are installed
if ! "$VENV_PATH/bin/python" -c "import atlassian" 2>/dev/null; then
echo "⚠ Dependencies may not be fully installed"
echo "Try running: source $VENV_PATH/bin/activate && pip install -r $PLUGIN_ROOT/requirements.txt"
else
echo "✓ jira plugin environment is ready!"
fi
After running this skill, you should see:
.claude/jira/venvIf bootstrap fails:
.claude/ directoryIf dependencies fail to install:
source ".claude/jira/venv/bin/activate"
pip install -r "$PLUGIN_ROOT/requirements.txt" --verbose
npx claudepluginhub rhuss/cc-jira --plugin jiraSets up Jira Cloud integration by verifying credentials, discovering custom fields and projects, and persisting results as version-controlled JSON caches. Idempotent setup command.
Opt-in Atlassian/Jira integration via acli for creating work items, transitioning statuses, adding comments, and linking PRs. Activates when working with Jira, Atlassian, or acli.
Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.