validate-chalk
Audit the .chalk/ directory to verify that chalk.json and PROFILE docs are complete, correct, and sufficient for skills to operate. Reports gaps and optionally fixes them.
When to Use
- Before running skills that depend on project context (capture-pr-visuals, create-pr, etc.)
- After initial setup to verify completeness
- Periodically to detect stale docs
- In CI to enforce chalk quality
Workflow
Step 1: Check chalk.json exists and is valid
- Read
.chalk/chalk.json - Validate required fields:
version— must be"1.0"project.name— must exist and be non-empty
- Check recommended fields and report if missing:
project.description,project.language,project.framework,project.type
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
23create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13