temper

Enforce two-step evidence capture and review before committing code changes.

2|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/cankush625/temper --skill temper-cankush625
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: temper
Source: https://github.com/cankush625/temper/tree/main/skills/temper
Command: npx skills add https://github.com/cankush625/temper --skill temper-cankush625

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires temper, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The temper Skill combats the issue of unverified claims in code development by enforcing a two-step process of evidence capture and review before committing changes.

Core Features & Use Cases

  • Anti-Bluffing Verification: Ensures that code claims are backed by evidence through command receipts and review receipts.
  • Task Management: Organizes tasks into a JSON plan, with status tracking and evidence capture.
  • Review Process: Facilitates a skeptical review process to validate code changes before committing.

Quick Start

Run the temper skill to start an anti-bluffing work session for a task in your project.

Frequently Asked Questions about temper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce code integrity verification before committing changes in Claude Code?

Code integrity verification is enforced by automating a two-step evidence capture and skeptical review process before any commit is executed. This requires the temper tool to validate code claims through command receipts.

What is anti-bluffing verification for software development?

Anti-bluffing verification ensures code claims are backed by evidence by requiring command receipts and review receipts before changes are committed. This combats unverified claims during development.

How do I capture evidence for code reviews before a commit process?

You capture evidence by organizing tasks into a JSON plan with status tracking, then executing commands that generate receipts. These receipts are reviewed to validate changes before committing.

Do I need the temper tool to run anti-bluffing work sessions?

Yes, the temper tool is a required dependency for running anti-bluffing work sessions. It integrates directly with Claude Code repositories to automate the evidence capture process.

Can I use task management tracking to prevent unverified code claims?

Task management tracking prevents unverified claims by organizing tasks into a JSON plan with ongoing status updates. This structure ensures evidence is captured and reviewed before committing.

What are the limitations of using a two-step evidence capture process for commits?

The two-step evidence capture process requires the temper tool and is specifically designed for Claude Code repositories. It mandates a skeptical review step, which adds overhead to the commit workflow.