Total Skills
18
Author Profile: jlissner
Skills published by jlissner with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
grimoire-apply
0
Stars
0
Downloads
0
grimoire-audit
0
Stars
0
Downloads
0
grimoire-branch-guard
0
Stars
0
Downloads
0
grimoire-bug-explore
0
Stars
0
Downloads
0
grimoire-bug-report
0
Stars
0
Downloads
0
grimoire-bug-session
0
Stars
0
Downloads
0
grimoire-bug
0
Stars
0
Downloads
0
grimoire-bug-triage
0
Stars
0
Downloads
0
Published Skills
grimoire-apply
Implement tasks from a planned grimoire change with strict red-green BDD. Use when tasks.md exists and is ready for implementation.
Repository SourceNeeds Review
grimoire-audit
Audit an existing codebase to discover undocumented features and architecture decisions. Use when onboarding an existing project to grimoire.
Repository SourceNeeds Review
grimoire-branch-guard
Enforce branch hygiene when starting a new feature. Use when the user requests a new feature and the current branch is dirty, mid-feature, or otherwise unfit for piggy-backing. Creates an appropriately named branch before any drafting or planning begins.
Repository SourceNeeds Review
grimoire-bug-explore
AI-guided exploratory testing that finds gaps in feature coverage, generates edge case scenarios, and identifies untested paths. Use when you want to proactively find bugs before users do.
Repository SourceNeeds Review
grimoire-bug-report
Structured bug reporting for testers. Guides creation of reproducible, context-rich bug reports that link to existing feature specs. Accepts output from testing tools (Playwright, Cypress, etc.) via MCP or directly. Use when a tester or non-developer needs to file a bug.
Repository SourceNeeds Review
grimoire-bug-session
Guided exploratory testing sessions with charter, progress tracking, session notes, and debrief. Use when a tester wants to spend focused time exploring an area of the application.
Repository SourceNeeds Review
grimoire-bug
Disciplined bug fix workflow with reproduction-first methodology. Use when the user reports a bug or defect that needs fixing.
Repository SourceNeeds Review
grimoire-bug-triage
Triage bug reports — classify the root cause, route to the right team (code, infra, config, data, third-party, docs), and communicate decisions back. Reads from local reports or external tickets via MCP. Use when picking up a bug report.
Repository SourceNeeds Review
grimoire-commit
Write a contextual commit message from staged changes and active grimoire change context. Use when the user asks to commit or after completing a task.
Repository SourceNeeds Review
grimoire-discover
Generate area docs and data schema from a codebase snapshot. Use when initializing grimoire on an existing project or when codebase structure has changed significantly.
Repository SourceNeeds Review
grimoire-draft
Draft or update Gherkin features and MADR architecture decisions collaboratively with the user. Use when the user describes new functionality, requirements, or architecture choices.
Repository SourceNeeds Review
grimoire-plan
Derive implementation tasks from approved Gherkin features and MADR decisions. Use when features are approved and ready for task breakdown.
Repository SourceNeeds Review
grimoire-pr-review
Review a teammate's pull request using the same multi-persona lens as pre-commit review, but against the actual diff. Fetches the PR, loads linked grimoire artifacts via the Change trailer, and produces structured findings suitable for PR comments.
Repository SourceNeeds Review
grimoire-pr
Generate a pull request description from grimoire change artifacts with optional post-implementation LLM review. Use when the user is ready to create a PR.
Repository SourceNeeds Review
grimoire-refactor
Systematically find, prioritize, and plan tech debt reduction. Use when the user wants to identify and address code quality issues, complexity, or duplication.
Repository SourceNeeds Review
grimoire-remove
Remove a feature or deprecate a decision through a tracked, deliberate change. Use when the user wants to decommission functionality with full impact assessment.
Repository SourceNeeds Review
grimoire-review
Multi-perspective design review before coding begins. Expert personas validate the change for completeness, feasibility, security, and data integrity. Use after draft/plan, before apply.
Repository SourceNeeds Review
grimoire-verify
Verify that implementation matches feature specs and decision records. Use after apply is complete, before archiving the change.
Repository SourceNeeds Review