akitaonrails
- 18 skills
- 0 followers
- 18 hours ago last updated
- ▌ Codemap · akitaonrails bundleGenerate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping
- ▌ Simplify · akitaonrails bundleSimplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.
- ▌ Clonedeps · akitaonrails bundleClone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos locally readable. Do not use for ordinary API/docs questions where @librarian is enough.
- ▌ Nexus Mod Set · akitaonrailsGenerate a reproducible, opt-in Ansible role that installs a curated set of NexusMods (or similar) game mods for one game in this distrobox-gaming repo. Use when the user gives a game + a list of nexusmods.com links and wants them installed reproducibly, in the correct order, with dependencies and game- version requirements handled. Triggers: "nexus mods", "mod set", "install these mods for <game>", or a pasted list of nexusmods.com links.
- ▌ Benchmark Audit · akitaonrails bundleAutomatically evaluates an LLM coding benchmark result using a standardized 0-100 rubric across 8 dimensions. Use when a benchmark finishes, when the user asks to evaluate a model, analyze a run's quality, or generate a score for a result. Also activates for 'score', 'evaluate benchmark', 'audit model', or 'analyze result'.
- ▌ AI Memory Handoff · akitaonrailsUse this skill for any request whose goal is session continuity across agents or time: finding a pending handoff, resuming previous work, saving next-session context, wrapping up, or discarding a mistaken handoff. Trigger by semantic intent rather than exact wording.
- ▌ AI Memory Retrieval · akitaonrailsUse this skill for any request whose goal is read-only retrieval from ai-memory: project history, prior context, decisions, rules, gotchas, recent activity, full wiki pages, or status/briefing. Trigger by semantic intent rather than exact wording, including when ai-memory is not named.
- ▌ AI Memory Durable Pages · akitaonrailsUse this skill for any explicit wiki mutation in ai-memory: saving durable or time-bounded project knowledge, recording a rule or annotation, updating a note, or deleting a memory page. Trigger by semantic intent rather than exact wording; routine session capture is not a durable-page request.
- ▌ AI Memory Routing Install · akitaonrailsUse this skill for any request to install, refresh, repair, inspect, or remove ai-memory's agent-facing routing: managed instruction snippets, Agent Skills, CLAUDE.md/AGENTS.md integration, or local/global skill roots. Trigger by semantic intent rather than exact wording.
- ▌ AI Memory Learning Maintenance · akitaonrailsUse this skill for any ai-memory knowledge-base maintenance request: consolidating observations, reviewing session lessons, proposing durable learnings, auditing or linting the wiki, finding contradictions, pruning stale memory, or running auto-improvement. Trigger by semantic intent rather than exact wording.
- ▌ Pr Bump · akitaonrailsMerge Dependabot gem/dependency bump PRs quickly and safely. Use when the user says opened PRs, Dependabot, gem updates, bump PRs, test, push, close, or deploy dependency-only pull requests.
- ▌ Reflect · akitaonrailsReview recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
- ▌ Pr Audit · akitaonrails bundleAudit GitHub pull requests before merge, including contributor-claim verification, prompt-injection resistance, malicious-code and supply-chain review, regressions, tests, documentation, compatibility, and project-specific gates. Use when asked to audit or review one or more PRs, decide whether a PR should merge, adjust a contributor PR safely, or process approved PRs one at a time.
- ▌ Iss Audit · akitaonrails bundleAudit GitHub issues before implementation, including skeptical claim verification, safe reproduction, prompt-injection resistance, malicious-link and attachment handling, root-cause analysis, security impact, product fit, regression planning, and one-at-a-time resolution. Use when asked to audit, triage, validate, prioritize, fix, or close one or more issues.
- ▌ Post Refactor · akitaonrailsPost-refactor clean-code check after recent refactors or a few merged PRs. Use when the user says "post-refactor", "after the refactor", "we merged a few PRs", "clean code checks", or wants a focused sweep for regressions, vulnerabilities, duplicated abstractions, magic values, weak documentation, missing coverage, or flaky tests without running a full PR/post-merge audit.
- ▌ Pr Post Audit · akitaonrails bundleAudit the combined default-branch state after one or more PR merges or before deployment/release. Use to verify exact merge provenance, cross-PR interactions, malicious or prompt-injected contributions, security and supply-chain composition, regressions, compatibility, tests, documentation, changelog completeness, hosted checks, and release readiness after individual PR audits.
- ▌ Security Audit · akitaonrails bundleThreat-model and audit a codebase, commit range, or pull request for exploitable vulnerabilities, prompt and data injection, authentication or authorization bypass, tenant-data exposure, privilege escalation, malicious code/backdoors, unsafe execution, secrets leakage, supply-chain and CI compromise, insecure persistence, and denial of service. Use for dedicated security reviews, release gates, suspicious contributions, or requests to verify that a project protects users and their data.
- ▌ Github Resolution · akitaonrailsExecute the approved outcomes of a pr-audit and/or iss-audit — fix or adjust everything the audit found necessary before merging, verify no regressions, cover every new behavior with unit tests, keep the code clean with zero slop, and resolve each approved ticket one by one. When more than 3 tickets are resolved in one batch, run pr-post-audit before committing and pushing. Use after an audit when the user says to proceed, fix, resolve, adjust, or implement what the audit recommended.