Loading...
Loading...
Found 24 Skills
Proceed with implementation based on the TODO list in Spec.md. Execute review→check→commit after each task is completed.
Multi-language code quality gate with auto-detection and language-specific linters. Use when user asks to "run quality checks", "quality gate", "lint all", "check everything", "pre-commit checks", or "is this code ready to commit". Use for verifying code quality across polyglot repos. Do NOT use for single-language linting (use code-linting) or comprehensive code review (use systematic-code-review).
Use when completing a task, implementing a feature, or before committing to verify work meets requirements and coding standards. Triggers: task completion, pre-commit check, pre-merge validation, plan alignment verification, post-refactor quality gate.
Review staged git changes against an issue. Produces a structured improvement plan — no edits applied. Also identifies test file compaction opportunities. Use when asked to check, review, or validate staged work before committing. Part 2 of 3 in the issue-review-two-phases workflow.
Use this skill as foundation for git workflows. Use when verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs. Do not use when full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep.
Remove AI slop from the code a branch changed, before a commit and without changing behavior: narrating comments, guards on states the types or the boundary already rule out, dead compatibility paths, unrelated edits, one-caller wrappers and speculative abstractions, casts that silence the type checker, and nesting an early return flattens. Use for /deslop, deslop it, clean the diff, strip the slop, or before any commit. Code only. The unslop skill cleans prose and the no-comments skill reviews comments.
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.
Commit standards for Engram contributors. Trigger: Any commit creation, review, or branch cleanup.
Diff Review - analyzes code changes and provides structured feedback before commit
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Gate every commit — typecheck, lint, smoke, then promote draft to wiki