with one click
devops-policy-template-maintainer
// Maintain this reusable AI-assisted DevOps policy template. Use task-specific skills for issue, MR, and commit drafting.
// Maintain this reusable AI-assisted DevOps policy template. Use task-specific skills for issue, MR, and commit drafting.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | devops-policy-template-maintainer |
| description | Maintain this reusable AI-assisted DevOps policy template. Use task-specific skills for issue, MR, and commit drafting. |
| license | MIT |
Use this skill when editing this repository.
Keep this repository reusable across projects. Prefer fewer clearer files over more guidance. Every changed line must support policy distribution, policy maintenance, or agent operation.
AI_DEVELOPMENT_POLICY.md focused on enforceable AI-assisted rules.CONTRIBUTING.md focused on human Git workflow..codex/agents/*.toml as the active core execution definitions..codex/agents/_archive/*.toml as legacy references only.docs/agents/*.md as short selection guidance.skills/*/SKILL.md.Do not assume repository-local skills/*/SKILL.md files are auto-loaded.
Read the matching task rule before creating issue, MR, or commit artifacts.
The user does not need to mention the skill name.
skills/write-issue/SKILL.mdskills/write-mr/SKILL.mdskills/write-commit/SKILL.mdskills/spec/SKILL.mdskills/build/SKILL.mdskills/review/SKILL.mdspec: skills/spec/SKILL.md + issue-agent.build: skills/build/SKILL.md + backend-developer.review: skills/review/SKILL.md + code-reviewer.secure: use security-auditor.docs: use docs-agent.Keep skills/spec/SKILL.md, skills/build/SKILL.md, and skills/review/SKILL.md short AI execution aids.
Use archived agents only as references.
Do not add specialized agents unless the same need appears repeatedly and cannot be handled by the core set.
Before editing, identify:
Do not add speculative configuration, optional process branches, or broad refactors. If two interpretations would produce different template behavior, ask first.
For document-only changes, run a repository text check such as:
git diff --check
For script changes, run the changed script with a safe target or --dry-run when available.