strikes

Display the current session's strike count and recorded violation reasons.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/devseunggwan/praxis --skill strikes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strikes
Source: https://github.com/devseunggwan/praxis/tree/main/skills/strikes
Command: npx skills add https://github.com/devseunggwan/praxis --skill strikes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users quickly see the current session's strike count (0-3) and the recorded violation reasons, reducing ambiguity during troubleshooting or discipline workflows.

Core Features & Use Cases

  • Display current strikes: Shows the header line like Strikes: N/3 for immediate visibility.
  • List violation reasons: Presents the Reasons list verbatim to support auditing and replay.
  • Deterministic output: Outputs the exact header and reasons without interpretation for reliable record-keeping.

Quick Start

Ask for the current strike status by saying "strikes status" to retrieve the live output.

Frequently Asked Questions about strikes

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

FAQPage Schema
How do I check the current Claude Code session strike status?

Check the Claude Code session strike status by running the /strikes command. It outputs the header line Strikes: N/3 and the verbatim Reasons list for immediate visibility and auditing.

What does the strikes output format look like in Claude Code?

The strikes output format is deterministic, displaying the header line Strikes: N/3 followed by a verbatim list of violation reasons. It outputs exact data without interpretation for reliable record-keeping.

Can I use localized terms to check my session strike count?

Yes, you can check the session strike count using localized terms like 몇 진. The skill recognizes these alongside standard commands like strike status to retrieve live output.

How do I view violation reasons recorded during an active Claude Code session?

View recorded violation reasons by requesting the strike status. The skill relies on the strike-counter Bash script to present the Reasons list verbatim, supporting auditing and replay.

Do I need any dependencies to display the strike state in Claude Code?

No dependencies are required to display the strike state. The skill relies on the built-in strike-counter Bash script at the plugin hooks directory to output the session state deterministically.