dirien/yet-another-agent-harness / .claude/skills/agent-rules
agent-rules
FlaggedUse when creating or updating AGENTS.md files, .github/copilot-instructions.md, or other AI agent rule files, onboarding AI agents to a project, standardizing agent documentation, or when anyone mentions AGENTS.md, agent rules, project onboarding, or codebase documentation for AI agents.
assets/scoped/gitlab-ci.md
View on GitHub<!-- Managed by agent: keep sections and order; edit content, not structure. Last updated: {{TIMESTAMP}} -->
# AGENTS.md — {{SCOPE_NAME}}
<!-- AGENTS-GENERATED:START overview -->
## Overview
{{SCOPE_DESCRIPTION}}
<!-- AGENTS-GENERATED:END overview -->
<!-- AGENTS-GENERATED:START filemap -->
## Key Files
{{SCOPE_FILE_MAP}}
<!-- AGENTS-GENERATED:END filemap -->
<!-- AGENTS-GENERATED:START golden-samples -->
## Golden Samples (follow these patterns)
{{SCOPE_GOLDEN_SAMPLES}}
<!-- AGENTS-GENERATED:END golden-samples -->
<!-- AGENTS-GENERATED:START setup -->
## Pipeline configuration
{{JOB_COUNT_LINE}}
{{INCLUDES_LINE}}
<!-- AGENTS-GENERATED:END setup -->
<!-- AGENTS-GENERATED:START structure -->
## File structure
```
.gitlab-ci.yml → Main pipeline configuration
.gitlab/
ci/
templates/ → Reusable job templates
jobs/ → Job definitions (included)
CODEOWNERS → Code ownership
```
<!-- AGENTS-GENERATED:END structure -->
<!-- AGENTS-GENERATED:START code-style -->
## Pipeline conventions
- Use **stages** to organize job execution order
- **Extend templates** with `extends:` for DRY jobs
- Use **rules:** instead of `only:/except:` (deprecated)
- **Cache dependencies** between jobs
- Use **artifacts** to pass files between stages
### Naming conventions
| Type | Convention | Example |
|------|------------|---------|
| Stage | lowercase | `build`, `test`, `deploy` |
| Job | kebab-case with stage prefix | `build-app`, `test-unit` |
| Variable | SCREAMING_SNAKE | `DEPLOY_ENV`, `CI_TOKEN` |
| Template | `.template-name` (dot prefix) | `.build-template` |
<!-- AGENTS-GENERATED:END code-style -->
<!-- AGENTS-GENERATED:START patterns -->
## Common patterns
### Basic pipeline structure
```yaml
stages:
- build
- test
- deploy
variables:
NODE_VERSION: "20"
build-app:
stage: build
image: node:${NODE_VERSION}
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/
expire_in: 1 hour
test-unit:
stage: test
needs: [build-app]
script:
- npm test
```
### Reusable job template
```yaml
.deploy-template:
stage: deploy
image: alpine:latest
before_script:
- apk add --no-cache curl
script:
- ./deploy.sh $ENVIRONMENT
deploy-staging:
extends: .deploy-template
variables:
ENVIRONMENT: staging
rules:
- if: $CI_COMMIT_BRANCH == "main"
deploy-production:
extends: .deploy-template
variables:
ENVIRONMENT: production
rules:
- if: $CI_COMMIT_TAG
when: manual
```
### Matrix builds (parallel)
```yaml
test:
stage: test
parallel:
matrix:
- NODE_VERSION: ["18", "20", "22"]
OS: ["alpine", "debian"]
image: node:${NODE_VERSION}-${OS}
script:
- npm test
```
### Include external files
```yaml
include:
- local: '.gitlab/ci/templates.yml'
- project: 'company/ci-templates'
ref: main
file: '/templates/docker.yml'
- template: Security/SAST.gitlab-ci.yml
```
<!-- AGENTS-GENERATED:END patterns -->
<!-- AGENTS-GENERATED:START security -->
## Security & safety
- Use **protected variables** for secrets (Settings > CI/CD > Variables)
- **Mask variables** to prevent log exposure
- Use **protected branches** for deployment jobs
- Enable **SAST/DAST** scanning templates
- **Pin Docker images** to specific versions/digests
- Use `rules:` with `$CI_COMMIT_TAG` for release workflows
- Review **merge request pipelines** before merging
<!-- AGENTS-GENERATED:END security -->
<!-- AGENTS-GENERATED:START checklist -->
## PR/commit checklist
- [ ] Pipeline syntax valid: use CI/CD > Editor > Validate
- [ ] Jobs use appropriate stages
- [ ] Sensitive variables are masked and protected
- [ ] Artifacts have reasonable `expire_in` values
- [ ] Cache keys are appropriate for the content
- [ ] Rules conditions are correct (not using deprecated only/except)
<!-- AGENTS-GENERATED:END checklist -->
<!-- AGENTS-GENERATED:START examples -->
## Patterns to Follow
> **Prefer looking at real code in this repo over generic examples.**
> See **Golden Samples** section above for files that demonstrate correct patterns.
<!-- AGENTS-GENERATED:END examples -->
<!-- AGENTS-GENERATED:START help -->
## When stuck
- GitLab CI docs: https://docs.gitlab.com/ee/ci/
- CI/CD YAML syntax: https://docs.gitlab.com/ee/ci/yaml/
- Predefined variables: https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
- Use the pipeline editor for validation: CI/CD > Editor
- Check existing `.gitlab-ci.yml` patterns in this repo
<!-- AGENTS-GENERATED:END help -->
## House Rules (project-specific)
<!-- This section is NOT auto-generated - add your project-specific rules here -->
{{HOUSE_RULES}}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |