Files
computer-playbook/CONTRIBUTING.md
T
kevinveenbirkenbachandClaude Opus 5 b291cb7620 feat(docs): report a code span that names a linkable directory
`roles/` set as inline code reads as a literal path, yet the directory
holds an index page the build resolves. Writing it as a link costs nothing
and gives the reader the page; leaving it as code hides it, which is how
this branch degraded six working references in one pass.

The lint strips markdown links from a line before scanning it, or it would
report the code span inside a finished link, and it skips fenced blocks. It
reads the index filenames from the same place the link lint does.

Two false-positive classes came out of the first run and shaped the rule. A
span of nothing but dots and slashes is a path word, not a path: '/' names a
filesystem in a table of mount points and '../' names the traversal an
argument must not perform. An absolute span is skipped because this
repository writes Keycloak group paths that way, and /roles/web-app-bluesky
is a group, not a folder.

35 spans across 12 files become links, and the documentation build resolves
every one of them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-25 20:09:41 +02:00

1.5 KiB

Contributing to Infinito.Nexus

This hub points to the detailed contributor guides for humans and AI assistants.

Quick Start 🚀

Follow these steps to make your first contribution.

  1. Create a fork and a branch with the right prefix.
  2. Set up your local environment.
  3. Make a focused change.
  4. Use the development guide.
  5. Push to your fork.
  6. Open a Pull Request with the right template.
  7. Request review and address feedback in your fork.

Start Here 📖

Requirements 📐

Functional requirements live under docs/requirements/ and follow a fixed format with a User Story and checkable Acceptance Criteria. See requirements.md for the authoring guide.

Repository Files 📋

Essential repository files covering agent rules, support, security, and community standards.