reasoning-semiformally
Apply semi-formal certificate reasoning to code analysis — patch verification, fault localization, patch equivalence. Use when reviewing patches, hunting bugs across scopes, comparing fixes, or when code reasoning requires tracing execution across files/modules. Triggers on code review, bug localization, patch comparison, name shadowing, scope analysis, regression checking.
git clone --depth 1 https://github.com/oaustegard/claude-skills /tmp/reasoning-semiformally && cp -r /tmp/reasoning-semiformally/reasoning-semiformally ~/.claude/skills/reasoning-semiformallySKILL.md
# Semi-Formal Code Reasoning Structured certificate templates that force mandatory checkpoints before conclusions. ## Skip Conditions Do NOT apply semi-formal reasoning when: - The change is trivial: docs, formatting, version bumps, config changes - The bug is locally obvious: typo, off-by-one in the same function, missing comma - No execution paths cross scope boundaries - The task is not code analysis (text editing, data extraction, summarization) If any skip condition is met, proceed with standard reasoning. ## Model-Specific Instructions **If you are Haiku-class (Haiku 4.5 or similar):** Read `haiku.md` in this skill directory. It contains full procedural templates with worked examples. **If you are Sonnet-class or above (Sonnet 4.6, Opus):** Read `sonnet.md` in this skill directory. It contains compact verification checkpoints. ## Composing Tasks For complex tasks, apply templates sequentially: 1. **Fault localization** to find the bug 2. **Patch verification** to validate a proposed fix 3. **Patch equivalence** to compare alternative fixes Each output feeds the next as premises.
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
Securely manages API credentials for multiple providers (Anthropic Claude, Google Gemini, GitHub). Use when skills need to access stored API keys for external service invocations.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
>-
>-
Browse Bluesky content via API and firehose - search posts, fetch user activity, sample trending topics, read feeds and lists, analyze and categorize accounts. Supports authenticated access for personalized feeds. Use for Bluesky research, user monitoring, trend analysis, feed reading, firehose sampling, account categorization.
Generate progressive disclosure indexes for GitHub repositories to use as Claude project knowledge. Use when setting up projects referencing external documentation, creating searchable indexes of technical blogs or knowledge bases, combining multiple repos into one index, or when user mentions "index", "github repo", "project knowledge", or "documentation reference".
Analyze and categorize Bluesky accounts by topic using keyword extraction. Use when users mention Bluesky account analysis, following/follower lists, topic discovery, account curation, or network analysis.