Assumptions

Generate an evidence-backed Assumptions ledger for a Git diff, feature, endpoint, worker, migration, or code path. Use when reviewing a change, asking what could break, preparing a release, finding edge cases, assessing deployment safety, analyzing retries or concurrency, or designing failure-focused tests.

20 stars 1 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Teycir/Assumptions --skill assumptions
Manual install
git clone --depth 1 https://github.com/Teycir/Assumptions.git /tmp/Assumptions
mkdir -p ~/.claude/skills
cp -r /tmp/Assumptions/. ~/.claude/skills/assumptions

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Assumptions

## Purpose

Identify the conditions a change silently depends on in order to work safely
in production.

Produce a structured ledger of:
- hidden assumptions, phrased as conditions that must hold
- repository evidence, with a file and line locator where available
- failure modes
- existing safeguards
- falsification tests
- recommended controls
- status, evidence confidence, and priority

This is not a generic code review. Do not report vague concerns.

## Core standard

Only report an assumption when you can provide all of the following:

1. The assumption stated as a falsifiable condition (what must hold, not
   what the current code does — see "Phrasing assumptions as conditions"
   below).
2. Direct evidence from code, tests, configuration, schema, documentation,
   or the Git diff, with a file path and line range when the tooling
   available can produce one. If a line range is unavailable, cite the
   file path and the symbol (function, route, migration file) instead.
   Never present a claim as repository evidence without a locator.

   **Locator accuracy hierarchy:**
   1. `path:lineStart-lineEnd` — only when the line-numbered source was
      actually opened and read, not inferred.
   2. `path — symbol` (function, route, migration file) — when a line
      range isn't available but the file was opened and the symbol
      identified.
   3. If neither is available, do not characterize the claim as direct
Read the full skill on GitHub

Details

Skill name
assumptions
Repository
Teycir/Assumptions
License
MIT
Repo updated
27 July 2026

FAQ

What does the Assumptions skill do?

Generate an evidence-backed Assumptions ledger for a Git diff, feature, endpoint, worker, migration, or code path. Use when reviewing a change, asking what could break, preparing a release, finding edge cases, assessing deployment safety, analyzing retries or concurrency, or designing failure-focused tests.

How do I install the Assumptions skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Teycir/Assumptions --skill assumptions. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Assumptions popular?

It lives in Teycir/Assumptions, which has 20 GitHub stars and 1 forks.

Related skills

Council Review

17

ngmeyer/council-review

Run any question, plan, PR, or code through a Diverse Multi-Agent Debate (DMAD) council of 5 AI advisors with distinct reasoning methods. Advisors collaborate, peer-review each other anonymously, and a chairman synthesizes a verdict. Empirically outperforms adversarial debate (M3MADBench 2026, DMAD ICLR 2025). Use when: 'council this', 'run the council', 'council review', 'pressure-test this', 'stress-test this', 'war room this', or when facing a genuine decision with stakes and tradeoffs.

Testing & QA

Plan and Build

17

jattanjie21/plan-and-build

Use when a user wants to plan and implement a new feature or bug fix from scratch. Triggers on requests like "I want to build X", "add a feature for Y", "fix Z", or when the user invokes /plan-and-build. Guides through clarifying questions, breaks work into small features, sets up a tasks folder, implements each feature with TDD (test first), and produces a manual testing guide when complete.

Testing & QA

Apple App Review Compliance

20

yohannescodes/apple-app-review-compliance

Audit Apple-platform applications, proposed features, code changes, App Store metadata, privacy practices, and submission readiness against Apple's current App Review Guidelines. Use during feature planning, PR review, pre-release QA, App Store rejection triage, or whenever StoreKit, HealthKit, permissions, authentication, user-generated content, or App Review policy matters.

Testing & QA

Qikly

19

gal-a/qikly

Write tests that can actually fail, by withholding the acceptance criteria from the agent that writes the code. Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specification is testable, or want an existing suite scored by planting faults in the code. Python modules, through the qikly tool. Also use whenever qikly or spec-driven testing is mentioned.

Testing & QAIn 1 list

Taiwan Exam Generator

19

niansia/taiwan-exam

Create original Taiwan GSAT/CAP (學測／會考) exams for 國綜、國寫、英文、數A、數B、社會、自然, with separate question/solution PDFs and official scope, difficulty, originality, answer, visual and layout QA.

Testing & QA

State of Paywalls 2026 By Adapty

26

vkharlan-adapt/state-of-paywalls-2026-skill

Answer questions from Adapty's State of Paywalls 2026 report and audit paywall designs against it: benchmarks by region and category, pricing, placement, A/B test ideas, and paywall screenshot reviews.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.