diff options
| author | Danilo M. <danix@danix.xyz> | 2026-07-11 13:00:29 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-07-11 13:00:29 +0200 |
| commit | 0da85a9dbf5c3a1ee80d47fc9fba730708c6bd8f (patch) | |
| tree | 9d9763000311e344236e4735384013892bea32fe /README.md | |
| parent | b6d1b8bd5249b9b406d9a4bb40c8d088801d8746 (diff) | |
| download | slackware-pentesting-suite-0da85a9dbf5c3a1ee80d47fc9fba730708c6bd8f.tar.gz slackware-pentesting-suite-0da85a9dbf5c3a1ee80d47fc9fba730708c6bd8f.zip | |
README: simplify tooling section, add Development Approach noticemain
Replace the detailed Git Hooks section with a one-line pointer to .extras/
(maintainer tooling, not needed to install packages). Add the AI-assisted
development disclosure at the bottom.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 29 |
1 files changed, 13 insertions, 16 deletions
@@ -61,19 +61,16 @@ Where a tool lives: > > The Powershell package is available on slackbuilds.org without modifications necessary so I removed it. -## Git Hooks - -This repo ships maintainer git hooks under `.extras/hooks/`. After cloning, -install them with: - -```bash -cp .extras/hooks/* .git/hooks/ && chmod 0755 .git/hooks/{pre,post}-commit -``` - -- **pre-commit** lints each changed package with `sbolint` and blocks the - commit on errors. It also refuses staged source archives (these are fetched - with `sbodl`, never committed). Bypass linting with `SBOLINT=no git commit`. -- **post-commit** offers to build an SBo submission tarball - (`SBo/<package>.tar.gz`) for any added or updated package. To answer the - prompt non-interactively, set `SBO_ARCHIVE=yes` or `SBO_ARCHIVE=no` in the - environment. +## Maintainer tooling + +The `.extras/` folder holds the tools used when maintaining this repo (git +hooks, version-tracking config, and helper scripts). They are not needed to +install any of the packages. + +## Development Approach + +This project is developed using AI-assisted tools. Code is generated with the help of AI based on human-provided specifications, design decisions, and iterative feedback. + +All contributions are reviewed, tested, and curated by the maintainer before being included in the codebase. AI is used as a productivity and exploration tool, while human oversight remains central to all decisions. + +The goal is to combine the flexibility of AI-assisted development with standard open-source practices such as transparency, review, and accountability. |