菜单
Runs the full gate sequence before raising a pull request on bash-logger. Covers linting, targeted tests, full test suite, code review checklist, commit message audit, PR description requirements, and branch hygiene. Use this skill before pushing to a shared branch or opening a PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Lints shell scripts and Markdown files in the bash-logger repository using the project's configured toolchain. Use this skill whenever checking code quality, fixing linting errors, or running lint as part of a pre-commit or pre-PR workflow.
Runs the bash-logger test suite — either the full suite or a targeted subset. Use this skill whenever running, selecting, or interpreting tests in this repository. Covers discovering available suites, choosing which to run after a change, correct invocation syntax, and reading test output.
Reviews code changes in bash-logger for security issues across all protected domains. Use this skill whenever adding new features that handle external input, changing sanitization behaviour, adding config options, or reviewing a PR for security. Covers input sanitization, file system safety, config injection, environment variable attacks, journal command validation, sensitive data handling, and unsafe flag governance.
Generates correctly formatted commit messages and pull request descriptions for this repository. Uses Conventional Commits / semantic-release format with issue references. Use this skill whenever writing, reviewing, or amending a commit message or drafting a PR title and body.
Adds new tests to the bash-logger test suite. Covers creating new test suites, adding tests to existing suites, correct use of assertions, isolation patterns, and the mandatory call registration pattern. Use this skill whenever writing, extending, or fixing tests in the tests/ directory.
| name | pre-pr-checks |
| description | Runs the full gate sequence before raising a pull request on bash-logger. Covers linting, targeted tests, full test suite, code review checklist, commit message audit, PR description requirements, and branch hygiene. Use this skill before pushing to a shared branch or opening a PR. |
Work through these steps in order. Each builds on the last.
make lint
Fix all ShellCheck and MarkdownLint failures. MarkdownLint auto-fixes most issues in-place, but does not re-stage the files — run git add on any modified files and re-run make lint before
continuing.
Identify relevant suites (see running-tests skill) and run them:
./tests/run_tests.sh <suite_name>
All must pass before continuing.
./tests/run_tests.sh
Zero failures required. Investigate all regressions before pushing.
logging.sh, install.sh, scripts)"$var"echo or set -x calls|| return follows every assertion$TEST_DIR.md filelogging.sh public API changed, README.md and docs/ updated* list markers, 2-space indent, ≤ 200 char linesgit log origin/main..HEAD --oneline
Every commit must follow <type>(<scope>): <subject> format. Amend any that do not:
git rebase -i origin/main # reword the offending commits
If a commit addresses a tracked issue, confirm Fixes #NNN or Refs #NNN is in the footer. See the writing-commits skill for the full specification.
<type>(<scope>): <subject> matching the primary intent of the PRgit fetch origin
git rebase origin/main
Resolve conflicts, then re-run the full test suite.
| Symptom | Cause | Fix |
|---|---|---|
| ShellCheck SC2086 | Unquoted variable | "$var" |
| ShellCheck SC2155 | Combined declare/assign | local x; x=$(...) |
| MarkdownLint MD004 | List marker is - | Change to * |
| Test not run | Call missing at bottom of suite | Add the call |
| Assertion not reached | Missing || return on prior assertion | Add || return |
| No release triggered | Commit type not release-triggering | Check .releaserc.json |