github.com/GingerGraham/bash-logger (link)

commit signals (36)

source signals (15)

• AGENTS.mdvia agents-md

  # bash-logger Agent Instructions
  
  This document provides guidance for AI agents contributing to the bash-logger project.
  Follow these standards when generating, modifying, or reviewing code.
  
  ## Agent Skills
  
  This repository provides skills in `.claude/skills/`. Supporting agents (GitHub Copilot,
  Claude Code, and others implementing the Agent Skills open standard) load these automatically.
  Each skill contains the authoritative, step-by-step workflow for its domain:
  
  * **[linting-code](.claude/skills/linting

• CLAUDE.mdvia claude-code

  AGENTS.md

• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .github/copilot-instructions.mdvia github-copilot

  ../AGENTS.md

• .claude/skills/linting-code/SKILL.mdvia unspecified

  ---
  name: linting-code
  description: >
    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.
  ---
  
  # Linting Code
  
  ## Tools and where configuration lives
  
  | Tool         | Checks                                          | Config                                                                    |
  | ------------ | ------

• .claude/skills/running-tests/SKILL.mdvia unspecified

  ---
  name: running-tests
  description: >
    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.
  ---
  
  # Running Tests
  
  ## Discover available suites first
  
  Never assume which suites exist. Always discover them at runtime:
  
  ```bash
  ls tests/test_*.sh | grep -v test_examp

• .claude/skills/writing-commits/SKILL.mdvia unspecified

  ---
  name: writing-commits
  description: >
    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.
  ---
  
  # Writing Commits and Pull Requests
  
  ## Commit message format
  
  ```
  <type>(<scope>): <subject>
  
  <body>
  
  <footer>
  ```
  
  Commit history drives automated versioning via `semantic-release`

• .claude/skills/writing-tests/SKILL.mdvia unspecified

  ---
  name: writing-tests
  description: >
    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.
  ---
  
  # Writing Tests
  
  Full assertion API reference is in `docs/testing.md`. Full contributor guide is in `docs/writing-tests.md`. This skill is the step-by-step agent workflow.

• .claude/skills/pre-pr-checks/SKILL.mdvia unspecified

  ---
  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.
  ---
  
  # Pre-PR Checks
  
  Work through these steps in order. Each builds on the last.
  
  ## 1. Lint
  
  ```bash
  make lint
  ```
  
  Fix all ShellCheck and MarkdownLint failures. MarkdownLint auto-

• .claude/skills/security-review/SKILL.mdvia unspecified

  ---
  name: security-review
  description: >
    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.
  ---
  
  # Security Review
  
  ## When to use 

ignorefile signals (0)

none