praxis-check
Checks code changes against ticket acceptance criteria.
Install
mkdir -p .claude/skills/praxis-check && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11142" && unzip -o skill.zip -d .claude/skills/praxis-check && rm skill.zipInstalls to .claude/skills/praxis-check
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Verify whether code changes cover the acceptance criteria of the active ticket. Use when the user invokes "/praxis check" with or without a ticket ID. Compares implemented code with acceptance criteria and local progression, generates a coverage report.Key capabilities
- →Verify acceptance criteria
- →Analyze code changes
- →Generate coverage reports
- →Update ticket progression
How it works
It compares implemented code against ticket acceptance criteria and generates a coverage report.
Inputs & outputs
When to use praxis-check
- →Verifying task completion
- →Reporting on feature coverage
- →Auditing ticket progress
About this skill
/praxis check [TICKET_KEY]
Verify acceptance criteria coverage against implemented changes.
Argument
Optional. Resolution per common.md.
References
- common.md — status model, paths, conventions
Workflow
0. Load config
Per common.md — Loading the provider (config only, no provider commands needed).
1. Read acceptance criteria
From the ticket file's Description: user story, scope, acceptance criteria. From Progression: current state.
2. Analyze changes
git diff main...HEAD+git log --oneline main...HEAD- Scan modified files to understand what was implemented
3. Detect PR
Per common.md — Detecting branch and PR.
4. Evaluate coverage
For each acceptance criterion, assign:
- ✅ Covered: implemented and/or tested
- ⚠️ Partially covered: incomplete or untested
- ❌ Not covered: no implementation found
- 🔄 Not verifiable: impossible to determine from code alone
5. Report
Display: criteria list with statuses, current progression, coverage score {X}/{Y}.
6. Update files
Ticket: update Progression, add to Avancement: {YYYY-MM-DD} : Vérification couverture — {X}/{Y} critères couverts.
Epic: update per common.md — Updating the epic file. Skip if epic is null.
7. Next steps
If gaps → suggest files to modify, tests to add.
If all covered → suggest /praxis post then /praxis done.
When not to use it
- →When no ticket is associated
- →When the code is not ready for verification
Prerequisites
Limitations
- →Depends on ticket description quality
- →Requires git history
How it compares
It automates the verification of task completion against specific criteria rather than manual review.
Compared to similar skills
praxis-check side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| praxis-check (this skill) | 0 | 4mo | No flags | Beginner |
| conductor-validator | 1 | 4mo | No flags | Beginner |
| agency-jira-workflow-steward | 0 | 4mo | Review | Intermediate |
| twig-sdlc | 0 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
conductor-validator
sickn33
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
agency-jira-workflow-steward
iFrescoo
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
twig-sdlc
PolyphonyRequiem
Run the end-to-end SDLC workflow for twig development. Takes an ADO work item or natural language prompt through planning, implementation, PR lifecycle, and close-out via Conductor multi-agent orchestration. Activate when asked to implement a feature end-to-end, run the full SDLC pipeline, or orches
drift-analysis
avifenesh
This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.
planning
citypaul
Planning work in small, known-good increments. Use when starting significant work or breaking down complex tasks.
gsd-plan-checker
toonight
Validates plans before execution to catch issues early