runkids

@runkids source repo

13 skills
0 followers
10 hours ago last updated

▌
Veto Changelog · runkids
Generate CHANGELOG.md entry from recent commits in conventional format. Use this skill whenever the user asks to: write release notes, generate a changelog, prepare a version release, document what changed between tags, or create a new CHANGELOG entry. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and version consistency with Cargo.toml.

0
installs
▌
Veto CLI E2e Test · runkids
Run isolated E2E tests from ai_docs/tests runbooks against the veto release binary. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in the sandbox. If you need to run a multi-step CLI validation sequence (init → check → gate → verify), this is the skill. Prefer this over ad-hoc command sequences for any test that follows a runbook or needs reproducible results.

0
installs
▌
Veto Devcontainer · runkids
Run CLI commands, tests, and debugging inside the veto devcontainer. Use this skill whenever you need to: execute veto CLI commands for verification, run cargo test, reproduce bugs, test rule matching, or perform any operation that requires an isolated Linux environment. If you are about to use Bash to run `veto`, `cargo test`, or `make test`, stop and use this skill first to ensure correct container execution in headless environments (no Touch ID, no keychain).

0
installs
▌
Veto Codebase Audit · runkids
Cross-validate CLI flags, rules, tests, and integrations for consistency across the veto codebase. Use this skill whenever the user asks to: audit the codebase, check for consistency issues, find undocumented flags, verify test coverage, validate rule definitions, or check integration completeness. This is a read-only audit — it reports issues but never modifies files. Use after large refactors, before releases, or whenever you suspect code has drifted.

0
installs
▌
Veto Implement Feature · runkids
Implement a feature or fix using TDD workflow in the veto Rust codebase. Use this skill whenever the user asks to: add a new rule category, implement a CLI subcommand, add an auth method, modify the risk engine, add a new integration (setup command), or write Rust code for veto. This skill enforces test-first development and follows veto's module conventions. If the request involves writing Rust code and tests, use this skill.

0
installs
▌
Feature Radar · runkids bundle
Full-cycle feature discovery, evaluation, and prioritization. Builds a persistent knowledge base at .feature-radar/ and runs a 6-phase workflow to recommend what to build next. Modes: full (all phases), quick (scan only), evaluate (prioritize), #N (deep-dive one). MUST use this skill whenever the user asks about feature priorities, roadmaps, what to build, or wants to evaluate/compare feature ideas — even if they don't say "feature radar" explicitly. Use when the user: - Asks "what should we build next?", "what's most impactful?", or similar - Wants to prioritize, rank, or compare features or backlog items - Needs roadmap planning, project direction, or strategic feature decisions - Says "help me prioritize", "review our backlog", "what are we missing" - Mentions .feature-radar/ directory or feature tracking - Wants periodic reassessment of deferred or open opportunities

0
installs
▌
Feature Radar Ref · runkids
Record external observations, ecosystem trends, and creative inspiration into .feature-radar/references/. MUST use this skill when the user mentions something interesting from outside their project — other tools, articles, approaches, or trends. Even casual mentions like "I saw a cool thing in X" should trigger this skill. Use when the user: - Says "I saw this cool thing in X's API", "check out how X handles this" - Shares a URL, article, talk, or research finding with relevant insights - Notes an ecosystem trend: new tools, standards, community patterns - Mentions a related project shipping a notable feature - Wants to bookmark external inspiration: "interesting approach", "save this" - Says "add reference", "log observation", "track this project" Do NOT use for internal learnings/patterns — that's feature-radar-learn's job. Do NOT use for prioritizing features — that's feature-radar's job.

0
installs
▌
Feature Radar Scan · runkids
Discover new feature opportunities from creative brainstorming, user feedback, ecosystem trends, and cross-project research. Writes results to .feature-radar/opportunities/. MUST use this skill when the user wants to GENERATE new ideas — not evaluate existing ones. Trigger on any request to brainstorm, explore, discover, or find new feature ideas, even casual ones like "I wonder what else we could do" or "give me ideas". Use when the user: - Asks "what else could we build?", "give me feature ideas", "what are we missing?" - Wants to brainstorm, explore new directions, or refresh the opportunity backlog - Says "scan ecosystem", "scan opportunities", "find new features" - Asks to review GitHub issues, community feedback, or adjacent tools for inspiration - Mentions "explore", "discover", or "new directions" in a feature context - Has a vague idea: "I have an idea", "what if we...", "I was thinking about..." Do NOT use for evaluating/prioritizing existing features — that's feature-radar's job.

0
installs
▌
Feature Radar Learn · runkids
Extract reusable patterns, architectural decisions, and pitfalls from completed work into .feature-radar/specs/. Captures the "why" behind choices so future sessions build on past experience. MUST use this skill when the user reflects on what worked/didn't, wants to document a decision, or mentions remembering a pattern for future use. Use when the user: - Says "remember this approach", "document this decision", "save this pattern" - Reflects: "that worked well", "lessons learned", "what did we learn" - Wants to capture: "don't forget this", "this was a good pattern" - Hit a dead end: "this didn't work because...", "avoid this approach" - Made a technical decision worth recording for posterity - Says "extract learnings" or "capture what we learned" Do NOT use for recording external observations — that's feature-radar-ref's job. Do NOT use for archiving completed features — that's feature-radar-archive's job.

0
installs
▌
Feature Radar Archive · runkids
Archive a completed, rejected, or covered feature into .feature-radar/archive/ with mandatory learning extraction. MUST use this skill whenever a feature reaches a terminal state — done, rejected, covered, deferred, or N/A. Even casual mentions like "we shipped X" or "X is done" should trigger this. The skill extracts learnings, derives new opportunities, and updates refs. Use when the user: - Says "we shipped X", "X is done", "X is complete", "we just finished X" - Rejects a feature: "we decided not to build X", "reject this", "doesn't fit" - Defers: "defer X", "postpone this", "revisit later", "not now" - Closes an opportunity: "close this opportunity", "mark as done", "archive this" - Mentions any feature reaching Done/Covered/Rejected/Deferred status Do NOT use for discovering new features — that's feature-radar-scan's job.

0
installs
▌
Feature Radar Validate · runkids bundle
Validate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file — catches format bugs like the 1024-char description limit before they break skill registration. Use when: - User says "validate", "check format", "lint skills", "run validation" - You just edited a SKILL.md (description, name, or body) — run proactively - You created or modified files in .feature-radar/ — run proactively - Before committing changes that touch skills/ or .feature-radar/ - User asks "are my skills valid?", "verify skills", "check skill format" IMPORTANT: Use this proactively after ANY edit to skills/ or .feature-radar/ files, even if the user doesn't ask for it. Format validation prevents silent breakage.

0
installs
▌
AI Hooks Integration · runkids bundle
Integrate lifecycle hooks across AI coding tools (Claude Code, Gemini CLI, Cursor, OpenCode) and any CLI. Use when: (1) installing/removing hooks, (2) creating OpenCode plugins, (3) setting up auto-formatting, testing, notifications, security policies, (4) wrapping CLI tools without hooks API. Triggers on: "add hook", "install hook", "hook integration", "PreToolUse", "PostToolUse", "PermissionRequest", "PostToolUseFailure", "SubagentStart", "SubagentStop", "TeammateIdle", "TaskCompleted", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "PreCompact", "beforeShellExecution", "auto-format", "notify on complete", "wrap CLI", "intercept command", "HTTP hook", "prompt hook", "agent hook", "async hook".

0
installs
▌
Skillshare · runkids bundle
Manages and syncs AI CLI skills and agents across 50+ tools from a single source. Use this skill whenever the user mentions "skillshare", runs skillshare commands, manages skills or agents (install, update, uninstall, sync, commit, audit, analyze, check, diff, search), or troubleshoots skill/agent configuration (orphaned symlinks, broken targets, sync issues). Covers both global (~/.config/skillshare/) and project (.skillshare/ or skillshare/) modes. Also use when: adding new AI tool targets (Claude, Cursor, Windsurf, etc.), setting target include/exclude filters or copy vs symlink mode, using backup/restore or trash recovery, piping skillshare output to scripts (--json), setting up CI/CD audit pipelines, building/sharing skill hubs (hub index, hub add), or working with agents (single .md files synced to agent-capable targets like Claude, Cursor, Augment, OpenCode) via positional `agents` filter or `--kind agent`, plus `.agentignore` and `enable`/`disable` for per-agent toggles.

0
installs

13 published skills