⚡ Bolt: Cache lowercased strings outside loops in YAML parser

[anchapin]

💡 What: Cached lowercased strings outside comprehensions in yaml_parser.py. 🎯 Why: To prevent redundant O(N) string allocations during string matching. 📊 Impact: Improves CPU execution time and memory usage for parsing. 🔬 Measurement: Observe reduction in overhead during YAML processing.

---

PR created automatically by Jules for task 7457097902162929496 started by @anchapin

Summary by Sourcery

Optimize YAML parsing string matching by caching lowercased values outside loops to avoid repeated allocations.

Enhancements:

• Cache lowercased skill names once per iteration when prioritizing skills for technologies.
• Precompute and reuse lowercased emphasize keywords and bullet text during experience filtering to reduce per-check overhead.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Caches lowercased strings outside of tight loops in the YAML parser to avoid repeated O(N) string allocations during case-insensitive matching, improving performance and memory usage.

Flow diagram for cached lowercasing in YAML parser loops

flowchart TD
    A[Start get_experience] --> B[Load variant_config]
    B --> C[Read emphasize_keywords]
    C --> D[Compute emphasize_keywords_lower once]
    D --> E[Loop over experience jobs]
    E --> F[Loop over bullets in job]
    F --> G[Compute text_lower once per bullet]
    G --> H{variant in emphasize_for
        or any kw in text_lower
        for kw in emphasize_keywords_lower}
    H -->|Yes| I[Append bullet to filtered_bullets]
    H -->|No| J[Skip bullet]
    I --> K[Next bullet/job]
    J --> K[Next bullet/job]
    K --> L[Return filtered_exp]

Loading

File-Level Changes

Change	Details	Files
Avoid repeated lowercasing of skill names when matching technologies in _prioritize_skills.	Introduce a cached lowercase version of the skill name per loop iteration. Use the cached lowercase skill name for technology substring checks instead of recomputing .lower() each time.	cli/utils/yaml_parser.py
Precompute lowercase emphasize keywords and bullet text to reduce repeated allocations in get_experience.	Create a list of lowercase emphasize keywords before iterating over experience bullets. Cache lowercase bullet text once per bullet before keyword matching. Update the keyword match condition to use the precomputed lowercase keywords and bullet text.	cli/utils/yaml_parser.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}