@semantic-release/gitlab
AAgent Guidelines for @semantic-release/gitlab
Install
agr install @semantic-release/gitlab --target codexWrites 1 file into AGENTS.md, pinned to git-e66ba89d.
- AGENTS.md
Document
Agent Guidelines for @semantic-release/gitlab
Commands
- Test:
npm testornpm run test - Lint:
npm run lint - Fix linting:
npm run lint:fix - Coverage: Tests include coverage reporting via c8
Code Style
- Node.js Version: 20.8.1+
- Module type: ES modules (
"type": "module") - Formatting: Prettier with 120 character line width and ES5 trailing commas
- Testing: AVA test framework
- Coverage: c8 for code coverage
Development Guidelines
- Perform minimal changes: Focus on the specific issue and make the smallest possible changes
- Focus on reviewers: Write clear, understandable code that is easy to review
- Use semantic commits: Follow conventional commit format (e.g.,
feat:,fix:,docs:,test:) - Run tests and formatting before committing: Always run
npm testandnpm run lintbefore making commits
Project Structure
lib/- Core library modulestest/- Test files (using AVA)index.js- Main entry point- Configuration files support semantic-release conventions
Testing Requirements
- All changes must maintain or improve test coverage
- Tests use nock for HTTP mocking
- Integration tests verify GitLab API interactions
- Run
npm testto execute the full test suite
Semantic Release Integration
This is a semantic-release plugin, so changes should follow semantic versioning principles and conventional commit formats for automated releases.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-e66ba89d15872026-08-06