adewale
5 verified skills4 total stars
guardrails
Code quality verification gates wired into the agent lifecycle. Use this skill whenever writing, modifying, reviewing, or debugging code — including new features, bug fixes, refactors, troubleshooting, CI/CD setup, or project bootstrapping. Also use when the user mentions "quality", "testing strategy", "CI pipeline", "guardrails", "debugging", or asks how to improve code reliability. If you're writing code or trying to understand why code isn't working, this skill applies.
development2
audit
Comprehensive audit toolkit with 14 audit types. Includes a pre-push branch audit (8-category checklist with Clean/Minor/Blocking verdicts) plus 13 deep-dive audits run via sub-agents: code quality, documentation brittleness, docs-code sync, language best practices, concurrency, resource management, test quality, feature completeness, performance, bug patterns, design philosophy compliance, security vulnerabilities, and UI design (CRAP principles). ALWAYS use this skill when the user wants to audit, review before pushing, check their branch, look for duplication or dead code, check docs, review test quality, find concurrency bugs, check resource leaks, analyse security or performance, review UI design, verify feature completeness, or check code against best practices or design principles.
tools1
audit
Comprehensive audit toolkit with 14 audit types. Includes a pre-push branch audit (8-category checklist with Clean/Minor/Blocking verdicts) plus 13 deep-dive audits run via sub-agents: code quality, documentation brittleness, docs-code sync, language best practices, concurrency, resource management, test quality, feature completeness, performance, bug patterns, design philosophy compliance, security vulnerabilities, and UI design (CRAP principles). ALWAYS use this skill when the user wants to audit, review before pushing, check their branch, look for duplication or dead code, check docs, review test quality, find concurrency bugs, check resource leaks, analyse security or performance, review UI design, verify feature completeness, or check code against best practices or design principles.
tools1
examples/reference/pages
--- layout: section transition: iris --- # The Skill Seven steps from intent to deck. Ten phases of compilation. --- transition: slide-left --- # Seven-Step Workflow ```mermaid {scale: 0.8} graph LR A["Mode"] --> B["Sources"] B --> C["Intake"] C --> D["Direction"] D --> E["Spec"] E --> F["Compile"] F --> G["Validate"] style A fill:#dde3ec,stroke:#3b5f87,color:#2e3440 style B fill:#dde3ec,stroke:#3b5f87,color:#2e3440 style C fill:#3b5f87,stroke:#3b5f87,color:#eceff4 style
development
slide-maker
Generate presentation decks grounded in real GitHub projects, or walk through a structured brief-to-slides process. Use when the user asks to create a presentation, slide deck, talk, pitch, keynote, or Slidev project — especially when they want slides based on an existing codebase, architecture, or project documentation.
development