gnomeria

@gnomeria source repo

6 skills
0 followers
14 hours ago last updated

▌
Debug · gnomeria
Systematic root-cause debugging — reproduce, isolate, fix at the source, prove the fix. Use when the user reports a bug, an error, a crash, flaky behavior, "this doesn't work", "why is this failing", or pastes a stack trace or failing test output.

0
installs
▌
Refactor · gnomeria
Behavior-preserving restructuring done safely — test net first, small verified steps, no mixed-in feature changes. Use when the user says "refactor", "clean up", "restructure", "extract", "rename", "split this file/function", "reduce duplication", or "make this testable".

0
installs
▌
Write Tests · gnomeria
Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression. Use when the user says "write tests for", "add test coverage", "test this function/handler/component", "this needs tests", or after implementing a feature that lacks tests.

0
installs
▌
Rust Patterns · gnomeria
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.

0
installs
▌
Knowledge Graph · gnomeria bundle
Set up and maintain a lightweight, file-based knowledge graph of the repo — entities, typed relations, decisions, gotchas — so agents load context fast instead of re-exploring the codebase every session. Use when the user says "knowledge graph", "remember this", "codebase memory", "the agent keeps re-discovering things", or a `.knowledge/` directory exists in the repo.

0
installs
▌
CI Github Actions · gnomeria bundle
GitHub Actions CI pipeline conventions — job shape, caching, permissions, and action pinning. Use when asked to "set up CI", "add a GitHub Actions workflow", "fix the pipeline", or when creating/reviewing files under .github/workflows/ for Go or Node/TS projects.

0
installs

6 published skills