github.com/MidnightBSD/src (link)

commit signals (292)

source signals (23)

• AGENTS.mdvia agents-md

  # AGENTS.md
  
  
  You are a senior software engineering assistant: precise, evidence-driven, direct, and safe.
  
  ## Priorities
  
  If rules conflict, lower-numbered priority wins:
  
  1. Correctness
  2. Evidence
  3. Safety
  4. Minimal changes
  5. Consistency
  6. Performance
  
  ## Boundaries
  
  - NEVER fabricate paths, commits, APIs, config keys, env vars, test results, or capabilities. State gaps explicitly.
  - NEVER game verification by weakening assertions, narrowing scope, reducing coverage, or skipping checks just to get a 

• contrib/mport/AGENTS.mdvia agents-md

  # Agent instructions (mport)
  
  ## Pre-commit checks (C)
  
  - Run `./skills/cppcheck-clang-format-precommit/scripts/precommit_c_sanity.sh` before committing C changes.
  - After that, run `./skills/splint-post-c-sanity/scripts/run_splint_on_staged.sh` to catch additional memory/contract issues with Splint.
  - These checks should ignore `external/` (third-party code); do not run precommit formatting/linting/splint over that directory.
  
  ## Splint annotations (security-sensitive areas)
  
  When modifying code that handl

• CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
  
  ## Project Overview
  
  This is the MidnightBSD operating system source tree — a BSD-derived desktop OS. The repository contains the full OS source including the kernel (`sys/`), userland utilities (`bin/`, `sbin/`, `usr.bin/`, `usr.sbin/`), libraries (`lib/`, `libexec/`), and contributed third-party software (`contrib/`).
  
  ## AI Policy (Required Reading)
  
  See `AI_POLICY.md` for the full polic

• contrib/mport/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
  
  
  You are a senior software engineering assistant: precise, evidence-driven, direct, and safe.
  
  ## Priorities
  
  If rules conflict, lower-numbered priority wins:
  
  1. Correctness
  2. Evidence
  3. Safety
  4. Minimal changes
  5. Consistency
  6. Performance
  
  ## Boundaries
  
  - NEVER fabricate paths, commits, APIs, config keys, env vars, test results, or capabilities. State gaps explicitly.
  - NEVER game ver

• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• contrib/mport/.claudedirectoryvia claude-code
• contrib/mport/.claudedirectoryvia claude-code
• .geminidirectoryvia gemini
• .agents/skills/splint-post-c-sanity/SKILL.mdvia unspecified

  ---
  name: splint-post-c-sanity
  description: Run splint after cppcheck/clang-format/clang-tidy precommit sanity to find memory issues, API misuse, and contract violations in staged C code (tolerates older C parser limitations).
  ---
  
  # Splint pass (after C sanity)
  
  Use this skill after running `cppcheck-clang-format-precommit` when you want an additional Splint pass focused on memory ownership, API misuse, and contract/annotation checking.
  
  ## Workflow
  
  1. Stage changes (`git add ...`).
  2. Run the C sanity sk

• contrib/mport/skills/splint-post-c-sanity/SKILL.mdvia unspecified

  ---
  name: splint-post-c-sanity
  description: Run splint after cppcheck/clang-format/clang-tidy precommit sanity to find memory issues, API misuse, and contract violations in staged C code (tolerates older C parser limitations).
  ---
  
  # Splint pass (after C sanity)
  
  Use this skill after running `cppcheck-clang-format-precommit` when you want an additional Splint pass focused on memory ownership, API misuse, and contract/annotation checking.
  
  ## Workflow
  
  1. Stage changes (`git add ...`).
  2. Run the C sanity sk

• .agents/skills/vendor-update/SKILL.mdvia unspecified

  ---
  name: vendor-update
  description: Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches). Handles vendor branch naming, Xlist pruning, tagging, git subtree merge, FreeBSD patch refresh, and stable branch merges — with mandatory user approval before every push, merge, or commit.
  ---
  
  # Vendor Branch Update
  
  Use this skill when you need to import a new upstream release of a third-party
  software package that lives in

• contrib/mport/skills/cppcheck-clang-format-precommit/SKILL.mdvia unspecified

  ---
  name: cppcheck-clang-format-precommit
  description: Run clang-format (prefer clang-format19), clang-tidy19, and cppcheck on staged C/C header changes before committing; auto-format then fail on serious diagnostics.
  ---
  
  # C pre-commit sanity (clang-format + clang-tidy + cppcheck)
  
  Use this skill when you’re about to `git commit` C/C header changes and want an automated preflight for serious bugs/vulns and formatting consistency.
  
  ## Workflow
  
  1. Stage your changes (`git add ...`).
  2. Run the pre-commit

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

  ---
  name: security-advisory
  description: Handle a security fix end to end for MidnightBSD src - triage a FreeBSD security advisory (FreeBSD-SA-*) or CVE against this tree, port the fix to master and both stable branches, add the UPDATING entry, and publish the matching MNBSD-YYYY-N advisory on the GitHub security advisories page. Use this whenever the user pastes or mentions a FreeBSD SA, a CVE, "does this affect us", "patch this on master/stable", or asks for a security advisory, even if they only ask for 

• .agents/skills/update-updating/SKILL.mdvia unspecified

  ---
  name: update-updating
  description: Add an entry to the UPDATING file at the repository root. Use whenever there is a security fix, vendor/third-party software update, behavioral change requiring user action, new stable branch creation, or a release. The UPDATING commit must be separate from any code changes so it can be cleanly cherry-picked to other branches.
  ---
  
  # Update UPDATING
  
  Use this skill when any of the following occur and need to be recorded for
  users who track -current or a stable branch:
  
  

• .agents/skills/cppcheck-clang-format-precommit/SKILL.mdvia unspecified

  ---
  name: cppcheck-clang-format-precommit
  description: Run clang-format (prefer clang-format19), clang-tidy19, and cppcheck on staged C/C header changes before committing; auto-format then fail on serious diagnostics.
  ---
  
  # C pre-commit sanity (clang-format + clang-tidy + cppcheck)
  
  Use this skill when you’re about to `git commit` C/C header changes and want an automated preflight for serious bugs/vulns and formatting consistency.
  
  ## Workflow
  
  1. Stage your changes (`git add ...`).
  2. Run the pre-commit

• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified

ignorefile signals (1)