skills/help-me/SKILL.md
Decide when to check command help before running shell or CLI commands. Use when Codex is about to execute a command and must judge whether it already understands the exact command form, flags, subcommands, or help path well enough to proceed, or should first consult `--help`, built-in `help`, `man`, or shell `help`.
npx skillsauth add narumiruna/agent-skills help-meInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Decide whether you know the exact command form well enough to run it. Keep the rule simple: if you can explain it clearly, run it; if you cannot, check help first.
<cmd> --help<cmd> <subcommand> --helphelp formman <cmd>type <cmd> or command -v <cmd> when the help path is unclear; if it is a shell builtin, use shell helpDo not use a hard whitelist. Judge familiarity on the exact command you are about to run.
pwd, ls src, git statusfind ... -exec ..., git rebase --rebase-merges, docker run ... --filter ...cd or export, run type cd and then help cddevelopment
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.