feat(ask): persist full Q&A entries with decisions to .qa.md

[yordis]

• Auditability requires capturing not just the question and answer, but the intention, assumptions, and the decision the answer led to — otherwise the rationale is lost as soon as the session ends.
• Making persistence mandatory (rather than opt-in) ensures every interview produces a durable record that can be referenced, reviewed, or revisited later.

[cursor]

PR Summary

Low Risk
Documentation-only changes to a Claude skill file; no runtime code, auth, or data paths are modified.

Overview
Session persistence is no longer optional. The skill must collect a session name up front, create <name>.qa.md at the git project root (via git rev-parse --show-toplevel), and record every exchange before asking the next question.

Each saved entry now follows a fixed template: numbered section title, question, intention, assumptions, answer, and an optional Supersedes: line when a later answer revises an earlier one (append-only history, no rewrites).

Bash is added to allowed-tools so the agent can resolve the repo root. Operational rules are tightened: write after each answer (no batching), and do not continue until the current entry is persisted.

^{Reviewed by Cursor Bugbot for commit 48787e7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

@yordis, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 58 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 87db6a58-f55d-4b10-9ae5-7b2f5866411c

📥 Commits

Reviewing files that changed from the base of the PR and between 3e92918 and 48787e7.

📒 Files selected for processing (1)

• plugins/trogonstack-ask/skills/ask-question/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/ask-1

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 431f85a. Configure here.}