Index of every page on this site: llms.txt
All skills
jetbrains avatar

/brainstorming

@e85862d
by jetbrainsjetbrains/thinkrail8.4k stars
532
Run it yourself

Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).

Use this Skill: https://skilld.dev/gh/jetbrains/thinkrail/brainstorming

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

fixing-a-bug.md

≈573 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Fixing a bug — brainstorming's bug branch

Entry: a bug report, with the task-spec open (spine step 3). Saves: the task-spec's Bug section. Next: spine step 8 (Build) — or spine step 5 when the "bug" turns out to be a feature.

A bug is a gap between what the product is meant to do and what it does. Settle the intended behavior before touching the code: it is confirmed and recorded in the task-spec here, which leads the fix the way a design leads a feature. The durable specs are amended at spine step 9, as for every change, so they describe what was actually built.

  1. Pin the report. Symptom (what happens), expected behavior (what should happen instead), and how to trigger it. Infer them from the request; ask only what is missing, in one round per the asking-user-questions concept skill.
  2. Reproduce when a safe command can show it — a failing test is best. Never run a destructive command to reproduce. If it can't be reproduced, record that and carry on.
  3. Locate the code that produces the behavior and the specs that govern that area (spec-graph).
  4. Classify by what those specs say about the expected behavior:
    • Silent — no spec covers it. The intended behavior is a product decision: confirm it with the user as an inference; spine step 9 adds it to the spec that should have stated it.
    • Wrong — a spec states the buggy or an outdated behavior. Confirm the correction with the user; spine step 9 corrects that spec.
    • Right — the spec already states the expected behavior; only the code is wrong. No question needed.
    • Feature — the code does what the specs intend, and the expected behavior was never intended. Tell the user it is a new capability and continue at spine step 5. Ask about the classification itself only when the evidence genuinely supports two of them.
  5. Record symptom, expected behavior, reproduction (or "unreproduced"), classification, and the confirmed intended behavior in the task-spec's Bug section. The intended behavior is the accepted design — there is no separate design review for a bug.
  6. Fix it test-first when practical: a regression test that fails before the fix and passes after. Continue at spine step 8.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts22d3 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    The brainstorming skill provides a structured manual workflow for designing features and fixing bugs through documentation and user interviews. It consists entirely of documentation, contains no executable scripts or remote dependencies, and includes safety-conscious instructions for bug reproduction.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at e85862d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last month

README badge

README badge for jetbrains/thinkrail/brainstorming