.claude-plugin/skills/add-shell-log-level/SKILL.md
# Skill: add-shell-log-level ## Overview | Field | Value | |-----------|-----------------------------------------------------------------------| | Date | 2026-02-20 | | Objective | Add a new log level function to a shared bash library that already defines its color variable but lacks the corresponding log function | | Outcome | Success — `log_debug()` added, pre
npx skillsauth add homericintelligence/projectscylla .claude-plugin/skills/add-shell-log-levelInstall 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.
| Field | Value |
|-----------|-----------------------------------------------------------------------|
| Date | 2026-02-20 |
| Objective | Add a new log level function to a shared bash library that already defines its color variable but lacks the corresponding log function |
| Outcome | Success — log_debug() added, pre-commit (ShellCheck) and syntax checks pass, PR merged via auto-merge |
| Issue | #781 |
| PR | #829 |
BLUE='\033[0;34m') but no function uses itlog_debug / log_trace / log_verbose level to a shared bash logging libraryAlways read the full script before editing so you understand the existing log function signatures.
# Check what log functions already exist
grep -n 'log_' scripts/docker_common.sh
The pattern used in scripts/docker_common.sh:
# Colors for output: RED=error, GREEN=info, YELLOW=warn, BLUE=debug
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
BLUE='\033[0;34m'
NC='\033[0m' # No Color
log_info() { echo -e "${GREEN}[INFO]${NC} $*"; }
log_warn() { echo -e "${YELLOW}[WARN]${NC} $*"; }
log_error() { echo -e "${RED}[ERROR]${NC} $*" >&2; }
log_debug() { echo -e "${BLUE}[DEBUG]${NC} $*"; }
Key details:
$* (not $1) for variadic messageslog_error writes to stderr (>&2); log_debug writes to stdoutbash -n scripts/docker_common.sh # parse-only, no execution
pre-commit run --files scripts/docker_common.sh # ShellCheck + whitespace hooks
Follow conventional commits:
feat(scripts): add log_debug() using BLUE color to docker_common.sh
Include Closes #<issue> in the commit message body.
don't ask permission mode. Fell back to direct git add / git commit / git push / gh pr create commands — all worked correctly.| Item | Value |
|------|-------|
| File changed | scripts/docker_common.sh |
| Lines changed | +8 / -4 (net +4) |
| ShellCheck result | Passed |
| Pre-commit result | All hooks passed |
| Bash syntax check | Passed |
| PR | #829 |
| Auto-merge | Enabled (rebase) |
BLUE color was previously removed (#722) because no function used it; this skill re-adds it with purpose$* change (from $1) is a low-risk improvement that handles multi-word arguments without quoting gymnasticsdevelopment
# Skill: docs-status-fix ## Overview | Field | Value | |------------|----------------------------------------------------| | Date | 2026-02-19 | | Category | documentation | | Objective | Fix stale "Current Status" in CLAUDE.md | | Issue | #753 | | PR | #810
tools
# Skill: preflight-closing-issues-fix ## Overview | Field | Value | |-------|-------| | Date | 2026-02-21 | | Issue | #802 | | PR | #912 | | Category | tooling | | Objective | Fix `preflight_check.sh` Check 3 false positives caused by free-text PR search matching issue numbers in unrelated PR titles/bodies | | Outcome | Success — 6 bash tests pass, all pre-commit hooks green, PR created with auto-merge | ## When to Use Trigger this skill when: - A preflight/guard script uses `gh pr list --s
tools
# Preflight Check Skill Propagation ## Overview | Field | Value | |-------|-------| | Date | 2026-02-21 | | Issue | #803 | | Objective | Add preflight check to `worktree-create` skill so developers bypassing `gh-implement-issue` still run the 6-check safety gate | | Outcome | Success — PR #917 created, auto-merge enabled | | Files Changed | `tests/claude-code/shared/skills/worktree/worktree-create/SKILL.md` | ## When to Use Use this pattern when: - A safety/quality gate exists in one entry-
tools
# Orphan Config Detection ## Overview | Field | Value | |------------|-----------------------------------------------------------------| | Date | 2026-02-20 | | Issue | #777 | | PR | #824 | | Objective | Warn when a `config/models/*.yaml` file