agentleFS
Sign inStart free
iamHrithikRajiamHrithikRaj/loom/skills/cpp-reliability/SKILL.md

cpp-reliability

Skill0 starsChanged 2 months agoMITView on GitHub

Analyze production C++ for ownership, lifetime, RAII, concurrency, error handling, exception safety, and material runtime costs. Use for reviews, regressions, design analysis, and reliability debugging.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    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:

    Check whether references, pointers, spans, views, callbacks, and captures can outlive their targets.

    line 12
  2. Distinctive:

    Treat shared ownership as a deliberate design decision, not a default.

    line 14
  3. Distinctive:

    Verify destruction ordering and shutdown behavior.

    line 15
  4. Distinctive:

    Check move operations for valid source and destination states.

    line 16
  5. Distinctive:

    Prefer RAII for memory, handles, locks, registrations, and transactions.

    line 20
  6. Distinctive:

    Verify cleanup after partial initialization and every error path.

    line 21
  7. Distinctive:

    Check exception guarantees where exceptions are enabled.

    line 22
  8. Distinctive:

    Ensure destructors cannot unexpectedly propagate failures.

    line 23
  9. Distinctive:

    Document shared state and its synchronization.

    line 27
  10. Distinctive:

    Check lock ordering, callback reentrancy, races, deadlocks, and cancellation.

    line 28
  11. Distinctive:

    Verify that atomics use an ordering strong enough for the invariant.

    line 29
  12. Distinctive:

    Avoid broad catches and success-shaped fallbacks.

    line 35
  13. Distinctive:

    Verify that failed operations leave state valid and recoverable.

    line 36
  14. Distinctive:

    Check retry safety, idempotency, and duplicate effects.

    line 37
  15. Distinctive:

    Look for avoidable allocation, copying, contention, and cache-unfriendly access only when they are material to the workload.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

C++ reliability

Ownership and lifetime

  • Identify the owner of every relevant object and resource.
  • Check whether references, pointers, spans, views, callbacks, and captures can outlive their targets.
  • Treat shared ownership as a deliberate design decision, not a default.
  • Verify destruction ordering and shutdown behavior.
  • Check move operations for valid source and destination states.

Resource safety

  • Prefer RAII for memory, handles, locks, registrations, and transactions.
  • Verify cleanup after partial initialization and every error path.
  • Check exception guarantees where exceptions are enabled.
  • Ensure destructors cannot unexpectedly propagate failures.

Concurrency

  • Document shared state and its synchronization.
  • Check lock ordering, callback reentrancy, races, deadlocks, and cancellation.
  • Verify that atomics use an ordering strong enough for the invariant.
  • Examine object lifetime across asynchronous work.

Error handling

  • Preserve actionable error context.
  • Avoid broad catches and success-shaped fallbacks.
  • Verify that failed operations leave state valid and recoverable.
  • Check retry safety, idempotency, and duplicate effects.

Performance

  • Look for avoidable allocation, copying, contention, and cache-unfriendly access only when they are material to the workload.
  • Require measurement before recommending complexity.
  • Include correctness and operational costs in every optimization tradeoff.

Findings

Report only issues with a concrete failure scenario or evidence-backed material risk. Include severity, location, scenario, evidence, correction, and confidence.

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