Risky Changes
Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.
Install
npx skills add davidondrej/skills --skill risky-changesgit clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/risky-changes ~/.claude/skills/risky-changesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Risky Changes A filter once passed every test but disabled ~99% of the feature on live data. Tests check code correctness; research and live measurement check whether a change is useful. ## When this applies Use for changes where being wrong is expensive or customer-visible: - Public API fields, filters, or response shaping - Dropping, transforming, or reordering upstream data - Billing, pricing, caps, or quotas - Defaults, thresholds, or provider request parameters - Unverified assumptions about external data or user behavior If unsure whether a change qualifies, apply this process. ## 1. Identify assumptions List the assumptions the change depends on. Mark which have evidence and which are still unverified. ## 2. Research before implementing Use available research tools and reliable sources. Investigate each distinct question separately, covering at least: - How do leading products handle this design decision? - What does real-world data look like: frequencies, shapes, and edge cases? - What do users or agents actually need? If evidence contradicts an assumption, reconsider the design before coding. If research is unavailable or inconclusive, state the gap; do not treat the assumption as verified. Do not ship while material assumptions remain unverified. ## 3. Measure real behavior Run 10–20+ realistic cases against the real endpoint or provider: - Base cases on real usage; vary topics, parameters, languages, and edge conditions.
Details
- Skill name
risky-changes- Repository
- davidondrej/skills
- Path
skills/risky-changes/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Risky Changes skill do?
Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.
How do I install the Risky Changes skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill risky-changes. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Risky Changes popular?
It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.
Related skills
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
4x4
4.3kdavidondrej/skills
Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.
Adr Verbatim
4.3kdavidondrej/skills
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
Connect Required Verification Information
2.1kstripe/ai
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
Pricing Page
7.7kMengTo/Skills
Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.
Release
2.1kShpigford/chops
Determine the next version, update the marketing site, and run the full release pipeline.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.