agentleFS
Sign inStart free
tethertotetherto/qvac/.cursor/rules/qip-triage.mdc

qvac / rules

Cursor rule697 starsChanged 18 days agoApache-2.0View on GitHub

When planning, implementing, or reviewing changes that clearly match technical proposal triggers, invoke qv-qip-triage before continuing. Prefer false negatives over false positives.

We split this qip-triage.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invoke for ordinary refactors, localized bug fixes, routine tests, documentation edits, or CI maintenance such as cache tuning, …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
qip-triage.mdc
---
description: When planning, implementing, or reviewing changes that clearly match technical proposal triggers, invoke qv-qip-triage before continuing. Prefer false negatives over false positives.
alwaysApply: false
---

# QIP proposal nudge

This rule does not define the workflow. It only nudges agents to invoke `qv-qip-triage` when appropriate.

## When to invoke

During planning, implementation, or PR review, invoke `qv-qip-triage` when a change clearly affects stable contracts, package boundaries, native/platform support, runtime/transport/storage choices, published NFRs, technical principles, or delivery architecture in CI.

## When not to invoke

Do not invoke for ordinary refactors, localized bug fixes, routine tests, documentation edits, or CI maintenance such as cache tuning, matrix cleanup, or flaky-test fixes unless they change one of the behaviors above.

## Outcome

The skill recommends creating a QIP. It is advisory only and must not block work mechanically.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free