[codex] remove bolding guidance from FinalRun skill

[droid-ash]

Summary

• remove bolding guidance from the FinalRun test generation skill
• replace it with neutral wording that tells authors to name visible controls clearly in plain language
• update the steps guidance to describe target screens, buttons, fields, and controls directly

Why

The skill was instructing authors to use bold UI labels in YAML-oriented test content. This change removes that styling guidance and keeps the instructions focused on clear, literal control names.

Impact

Authors following the skill now get plain-language guidance that better matches the intended YAML authoring style.

Validation

• rescanned skills/ for remaining Bold UI elements or Use bolding guidance
• reviewed the updated skills/generate-finalrun-test/SKILL.md wording

Root Cause

The authoring skill contained markdown-style bolding guidance in the section that teaches how to write FinalRun test steps.

Summary by CodeRabbit

Release Notes

• Documentation
  • Updated test flow writing guidance to emphasize clear, plain-language identification of screen elements and controls instead of formatting-based emphasis.

[coderabbitai]

Warning

Rate limit exceeded

@droid-ash has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 23 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 3 minutes and 23 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e73ec59a-c78a-4397-a54c-93a1752e5313

📥 Commits

Reviewing files that changed from the base of the PR and between c695157 and 3256402.

📒 Files selected for processing (1)

• skills/use-finalrun-cli/SKILL.md

📝 Walkthrough

Walkthrough

Documentation guidance for test flow composition was refined to prioritize direct, plain-language identification of UI controls over symbolic emphasis. Instructions shifted from bolding labels and icons to explicitly naming visible elements like buttons and screens in each test step.

Changes

Cohort / File(s)	Summary
Test Flow Guidance Documentation skills/generate-finalrun-test/SKILL.md	Updated test specification instructions to replace UI bolding emphasis with direct naming of controls; "Be specific" now references screen and control identification, and steps field guidance changed from bolding UI elements to naming targets directly in plain language.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [codex] Remove preconditions from test spec schema #28 — Both PRs modify the same skills/generate-finalrun-test/SKILL.md test-guidance documentation file.

Suggested reviewers

• arnoldlaishram

Poem

🐰 A hop through the docs, so clear and so bright,
Plain words beat the bold, they're just right,
No icons to squint, just buttons so neat,
Test flows now sparkle—what a sweet treat!

🚥 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 captures the main change: removal of bolding guidance from the FinalRun skill documentation. It is specific, clear, and directly reflects the primary modification.
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 codex/remove-bolding-guidance-skill

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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