All authors
Claude Skills by itsaspacestation
github.com/itsaspacestation12 skills0 installs24 views
- Bias AnalysisUse when comparing options with field reports, reviews, forum threads, surveys, reliability statistics, benchmarks, or user feedback, when writing a comparative study, or when asked whether X is more reliable, faster, or better than Y. Also use when a study needs a bias analysis section, or when the user questions whether the evidence is biased.Votes: 0GitHub stars: 2
- C4 GraphUse when drawing or converting a software architecture diagram following the C4 model — system context, container, or landscape — as a draw.io file rendered in VS Code or draw.io and embedded as .drawio.svg in GitLab, GitHub, or a README, from a text description, a DOT digraph, or a draw.io file or model. Also use when the user mentions C4, draw.io C4 shapes, line jumps, crossing arrows, diagram unreadable on dark theme, or asks to convert a .drawio file or a draw.io SVG export.Votes: 0GitHub stars: 2
- Code ReviewUse when the user asks for a full review of a change, pull request, or merge request against the personal checklist, covering design, tests, performance, security, and correctness — including local changes before pushing or opening an MR/PR. Also use when the user asks to read, address, answer, or reply to reviewer comments or threads, to post findings as applicable suggestions on GitLab or GitHub, or to prepare a plan from reviewer feedback, on any forge, including GitLab merge requests thro...Votes: 0GitHub stars: 2
- Create Grafana DashboardsUse when creating, reviewing, or extending a Grafana dashboard for a service, cloud resource, database, queue, or runtime: choosing metrics from the vendor's official monitoring page, laying out rows by RED or USE, trading paid metrics for log-derived panels, writing the dashboard README, or collecting screenshots. Also use when the user mentions CloudWatch, Prometheus, Loki, OpenTelemetry metrics, dashboard JSON, panel rows, RED method, or USE method.Votes: 0GitHub stars: 2
- DebugUse when a test fails, a build breaks, a bug is reported, behaviour is unexpected, performance drops, or an integration misbehaves, before proposing or applying any fix. Also use when a previous fix did not work, when the cause is unknown, or when the user says stop guessing.Votes: 0GitHub stars: 2
- Evidence Based AnalysisUse when analysing code, explaining how something works, writing or updating documentation, reviewing a change, debugging, tracing a CI or CD pipeline, or making any claim about the codebase. Also use when asked whether something is used, called, or dead code.Votes: 0GitHub stars: 2
- Git ConventionsUse when the user asks to commit, stage, branch, diff, write a commit message, or perform any git operation, and when the user asks to describe or summarise a change for review, such as a merge request or pull request description (MR, PR). Also use when discussing version control workflows or git safety.Votes: 0GitHub stars: 2
- PlanUse when the user asks to plan a task or feature before implementing, create a workspace, write a design doc or ADR, break work into sessions and tasks for autopilot, resume an active workspace, or integrate workspace artifacts into docs.Votes: 0GitHub stars: 2
- RetroUse when the user asks what would have prevented a mistake, asks for a retro, a post-mortem, or lessons, or asks how to stop something happening again. Also use when a session ended with a wrong fix, a missed convention, a slow search, or a repeated question, and at the end of a plan workspace before integration.Votes: 0GitHub stars: 2
- SkillUse when creating or editing a skill, agent, or command inside the ni plugin, when a skill does not trigger or triggers too often, when moving content between skills or into a reference file, or when the user asks how ni skills are structured, linked, tested, or installed.Votes: 0GitHub stars: 2
- Software EngineerUse when implementing a feature, fixing a bug, or refactoring in any codebase, when starting a task that needs the plan, test, implement, commit workflow, when the user asks to build, test, lint, format, or measure coverage on a project, when onboarding on or taking over an existing codebase, when reading a CI pipeline, Makefile, justfile, lock file, or wrapper script to find the build commands, or when the user asks about software architecture, domain modelling, clean or hexagonal architectu...Votes: 0GitHub stars: 2
- TddUse when writing tests, adding test coverage, implementing a feature or fix test-first, creating a failing test before code, or discussing red-green-refactor, acceptance tests, unit tests, or test strategy.Votes: 0GitHub stars: 2