decisionnerd · Agent Skills
共 24 个 Skill,均有经来源核对的实质文档。打开卡片可阅读原始说明,了解包内文件和安装方式。
agents
Work agent systems with command arguments: slap (emergency-fix stupid agent behavior and safely drain dumb workflows), analyze, optimize, design, and sub / sub-agents (delegate via subagents). Use when the user says agents, /agents , agent loops are thrashing, workflows need draining, or they want agent architecture, analysis, or parallel subagent execution.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
architect-it
Design or evolve the architecture of a system, module, or feature — survey the codebase, frame the bet (boundaries, placement, data flow), propose options with tradeoffs, record the decision where the repo keeps decisions, and plan the first slice. Use when the user says "architect it", asks to design a system or module, review architecture, plan boundaries before building, or untangle a structural bet that refactoring alone cannot fix. Not for behavior-preserving mechanics (use refactor-it), co
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
check-readiness
Review whether a GitHub issue is complete enough for its current stage and decide the next PR or closure action. Use before PR, before closing an issue, after merge, or when auditing a closed issue for regressions or missing scope. For pre-PR checks, use CodeRabbit CLI review; when an open PR exists and corrective review work is needed, use autofix.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
council
Convene independent reviews from three model providers and reconcile their findings. Use when the user says council, asks for a multi-model review, or wants several providers to challenge a plan or implementation.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
diagnose-bug
Diagnose backend, API, worker, data-pipeline, or algorithm bugs by reproducing with inputs/tests, checking invariants and complexity assumptions, correlating logs/traces/metrics, and inspecting code. Use when a user reports wrong outputs, failing tests, timeouts, races, incorrect algorithms, flaky jobs, bad API responses, or asks why a non-UI system is broken. Diagnose, then implement the smallest fix and a regression test in the same run; stop first only for diagnosis-only requests, live-data/o
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
document-it
Improve or add repository documentation for work just done or for product-docs gaps. Use when the user says "document it", asks for README/runbook/API notes, architecture notes, changelogs, ADRs, or DocSlime product docs. Default to a surgical update of the nearest accurate home after a change — do not scaffold or fill a DocSlime tree unless the altitude truly needs it. When product/requirements/testing/observability contracts are in play, use DocSlime structures and methods. Keep docs accurate
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
fix-it
Create an implementation-ready repair plan from diagnosis evidence — live-app (troubleshoot-app), backend/algo (diagnose-bug), failing URLs, logs, data-plane findings, or clearly reported breakage. Use when the user asks to \"fix it\", \"plan this fix\", or wants a plan before implementation — especially diagnose → fix-it → check-readiness → merge-it. Not for behavior-preserving structure work (refactor-it) or greenfield features without a failing contract.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
idk-now
When the user doesn't know what to do next: briefly survey environment, repo, docs, and git history; guide them through clarifying questions; then suggest next steps using DecisionNerd/dev-skills plus DocSlime, ProductFeeling, Impeccable, and any vendored skills in the repo space — aimed at an achievable goal toward why the project exists. Use when the user says "idk", "I don't know", "what now", "stuck", "lost", or /idk-now. Prefer recon when they already know the domain and need a tactical nex
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
issues
Work GitHub issues with command arguments: create/draft, update, critique, narrow, widen, merge, clean, refine, explain, document, close, reopen, search, and status. Default with only an issue identifier (and optional details) is execute completion work — plan/diagnose/implement/test/ready-check/merge — not issue-admin. Explicit commands still do admin. Rough idea with no identifier defaults to create. Use when the user asks about issues, /issues , drafting or improving an issue, or finishing tr
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
kiss
Audit goals, processes, systems, and plans for needless complexity — then recommend simplification only when it is warranted. Use when the user says "kiss", "keep it simple", "is this overcomplicated", "simplify this", or asks whether to cut scope/steps/architecture. Weigh risks and benefits of simplifying; do not default to reductionist cuts when complexity is earned. Simple also means a straightforward DAG to completion with right-sized tasks (not too small, not overly big). Pair with idk-now,
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
merge-it
Drive delivery through the repository's actual Integrate, Stage, or Ship path. Use when asked to land, merge, stage, ship, or finish a branch end-to-end. Open or update the PR, fix verified findings, and monitor current-head checks and reviews. Use merge-it prepare for ready-for-human-merge requests; it never merges or enables automatic merging. Merge mode verifies deployment and issue closure for the requested phase. Repository instructions define the release path.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
milestones
Work GitHub milestones with command arguments: create, update, critique, narrow, widen, merge, clean, refine, explain, document, close, status, and plan. Default with only a milestone identifier (and optional details) is execute completion work through Integrate — critical-path issue plan/implement, ready-check, and merge — not milestone-admin. Treat Stage/Ship as follow-ups; run them only when the user requests that phase. Explicit commands still do admin. Use when the user asks about milestone
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
modernize
Assess and update an old PR against its current base and architecture. Use when the user says modernize, rebase this PR, or bring an old branch up to date; recommend rework or closure when a rebase would preserve obsolete behavior.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
observe-it
Add or improve observability — structured logs, metrics, traces, errors, analytics, dashboards, and (for generative) LLM traces/scores. Use when the user says "observe it", asks for instrumentation, telemetry, alerting hooks, Langfuse/evals online, or "how do we know this works in prod". Match signals to quality regime A/B/C; prefer existing vendors (OTel, Sentry, PostHog, Langfuse house default for LLM). Ask before emitting PII or paid-volume storms.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
pulls
Work GitHub PRs with create/open, update, critique, scope, review, status/checks, watch/monitor, babysit, merge, and close commands. Use when the user asks about PRs or invokes pulls. Watch observes; babysit fixes verified failures and waits without merging. A bare PR identifier or no args on a current-branch PR defaults to Integrate completion via merge-it; explicit commands and ready-for-human-merge requests keep their own finish line. Stage/Ship run only when requested.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
recon
Scout the current work and recommend the next skill or action. Arguments: repo (whole-repo health), issue (deep implementation plan for an issue), milestone (milestone readiness and issue set). With no argument, read git logs and local branch state first to set scope, then suggest what to do next. Use when the user asks to recon, scout, assess, or \"what should I do next\". Knows DecisionNerd/dev-skills: agents, architect-it, idk-now, kiss, repos, issues, milestones, pulls, check-readiness, merg
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
refactor-it
Safely refactor code to improve structure, clarity, or testability without changing intended behavior. Use when the user says "refactor it", asks to clean up a module, extract helpers, reduce duplication, or prepare code for a feature — not for product behavior changes (use fix-it) or pure test adds (use test-it). Prefer small steps with tests green between steps.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
repos
Manage GitHub repositories: create/settings, split, combine, monorepo moves, architecture review, CI harden/simplify, and secrets (Pulumi ESC by default). Use when the user says repos, /repos , wants to carve or join repos, redesign monorepo layout, harden workflows, or set up secrets without long-lived GitHub Actions secrets. Mutating GitHub/Pulumi/cloud requires explicit approval.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
research-it
Research a technical or product question before building — APIs, libraries, prior art in-repo, external docs, tradeoffs, and a recommendation. Use when the user says "research it", asks what to use, compares options, wants an RFC-style brief, or needs evidence before implementation. Read-only; spikes and dependency adds are a separate, asked-for step. Hand off to fix-it / recon issue / issues create when ready to plan or track.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
sitrep
Provide a situation report on the current work: objective, done, in progress, blocked, next, and open questions. Default window is everything since the session start or the previous sitrep in this conversation, whichever is later. Evidence comes from session history plus read-only git/GitHub checks. Use when the user says \"sitrep\", \"situation report\", \"status report\", \"where are we\", \"what's happened\", \"catch me up\", or after a long run to summarise state.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
takeover
Take over an existing PR, branch, or agent thread while preserving contributor credit and unrelated work. Use when the user says takeover, take over this work, or continue another agent's implementation.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
test-it
Add, fix, or harden tests for the current change, issue, or failing suite. Use when the user says "test it", asks for coverage, regression tests, BDD evidence mapping, flaky-test stabilization, or CI test gaps. Name quality regime A/B/C first — wrong evidence is vibes. Prefer existing runners; if none exists, ask with options via the question tool. Pair with fix-it / diagnose-bug / check-readiness when tests prove a repair or readiness gate.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
tidy-up
Clean dangling workspaces/worktrees, stale branches, excess build artifacts, caches, and other leftover clutter. Arguments: scan/plan (inventory only), workspaces, artifacts, caches, branches, deep, and all. Use when the user says "tidy up", reclaim disk, remove stale worktrees, clear build junk, or prune leftover agent/dev debris. Always inventory first; delete only with approval unless the user already ordered that exact cleanup.
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
troubleshoot-app
Troubleshoot live web app failures by combining user-visible browser evidence, current project data-plane sources, logs, analytics, and local code inspection. Use when a user reports a broken or confusing app experience, asks why a deployed/live page is not working, provides a URL to inspect in Atlas or another browser, or asks to look at what they see. Diagnose, then implement the smallest fix and a regression test in the same run; stop first only for diagnosis-only requests, live-data/outside-
- 1小时安装量
- 3
- GitHub Stars
- 0
- 最近更新
- 11月4日
