meta: add AI agent rules and skills
Create a modular, context-aware style guide for AI code assistants. - Add nixos-architecture skill for .nix file generation and networking patterns - Add dns-management rule to enforce Bind9 SOA serial increments - Add cicd-networking rule for direct-IP runner authentication - Add git-workflow rule to enforce conventional and atomic commits
This commit is contained in:
parent
5a031b48ed
commit
3648b4d535
4 changed files with 95 additions and 0 deletions
13
.agent/rules/ci-cd-networking-constraints.md
Normal file
13
.agent/rules/ci-cd-networking-constraints.md
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
---
|
||||
name: cicd-networking
|
||||
description: Networking constraints for CI/CD workflow files (Gitea/GitHub Actions).
|
||||
globs: [".github/workflows/.yml", ".github/workflows/.yaml", ".gitea/workflows/.yml", ".gitea/workflows/.yaml"]
|
||||
---
|
||||
|
||||
# Bos55 CI/CD Networking Constraints
|
||||
|
||||
When generating or modifying CI/CD workflows, strictly follow these networking practices:
|
||||
|
||||
1. **IP-Based Login for Reliability**
|
||||
- When CI runners (like Gitea Actions) need to interact with internal services for authentication or deployment, always use direct IP addresses (e.g., `192.168.0.25`) for machine-to-machine login steps.
|
||||
- **Why?** This bypasses potential DNS resolution issues or delays within the isolated runner environment, ensuring maximum robustness during automated CI/CD runs.
|
||||
Loading…
Add table
Add a link
Reference in a new issue