// Attach the current AI session context to a Jira issue as a formatted comment. Useful for investigation, audit trail, handoff, debugging. Use when user says "attach session to Jira", "document on Jira", or "export context to AAP-XXXXX".
Automatically fix CVE vulnerabilities in Python dependencies for downstream projects. Queries Jira for unresolved CVEs, filters already-fixed issues, updates Pipfile and Pipfile.lock using container-based pipenv lock, creates MRs, and updates Jira. Use when the user mentions CVEs, vulnerabilities, security fixes, CVE remediation, dependency security updates, or asks to fix CVEs.
Add a new project to config.json with auto-detection and validation. Detects settings from directory, validates GitLab/Jira access, optionally configures Quay/Bonfire, generates initial knowledge. Use when user says "add project", "configure new repo".
Configure VMs with Ansible playbooks and ad-hoc commands. Run playbooks, install Galaxy roles, ad-hoc modules, inventory management, check mode. Use when configuring VMs or running Ansible against hosts.
Run smoke tests against API endpoints to verify availability and performance. Use after deploy_to_ephemeral, release_to_prod, or when debugging API connectivity.
Validate app-interface configuration and release readiness. Validates YAML, compares refs to live cluster, shows quotas, pending MRs. Use when user says "check app-interface", "app-interface validation".
Debug AWS RDS database issues by gathering infrastructure and database-level diagnostics. Use when user says "debug RDS", "RDS issues", "AWS database problems", or "check RDS health".
| name | attach-session-to-jira |
| description | Attach the current AI session context to a Jira issue as a formatted comment. Useful for investigation, audit trail, handoff, debugging. Use when user says "attach session to Jira", "document on Jira", or "export context to AAP-XXXXX". |
Exports AI session context and attaches it to a Jira issue. Includes session metadata, summary stats, key actions, related issue keys, and optional full transcript.
| Input | Type | Default | Purpose |
|---|---|---|---|
issue_key | string | required | Jira issue key (e.g., AAP-12345) |
session_id | string | "" | Session ID to export. Empty = active session |
include_transcript | bool | false | Include full conversation transcript (collapsible) |
^[A-Z]+-\d+$ (e.g., AAP-12345)session_info(session_id=session_id) — Get current/requested sessionjira_attach_session(issue_key=validated_issue_key, session_id=session_id, include_transcript=include_transcript)memory_session_log(action="Attached session context to {issue_key}", details="Include transcript: {include_transcript}"){attach_result}
---
## Next Steps
1. **View on Jira:** [AAP-12345](https://issues.redhat.com/browse/AAP-12345)
2. **Export locally:** session_export_context() for markdown/JSON
3. **Share with team:** Link the Jira issue in Slack or email
| Pattern | Message |
|---|---|
| Invalid issue key | Expected AAP-12345 format. Got: {input} |
| No active session | Run session_start() first |
| Failed to add comment | Check JIRA_JPAT, issue exists, VPN. Try jira_view_issue() |
session_info, jira_attach_session, memory_session_log