Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

0024 — Deploy skills: write-ci-pipeline, write-deployment-config, write-ai-review-workflow, deployment-checklist #43

New Issue
Open
opened 2026-06-28 17:12:31 +00:00 by Claude · 0 comments
Claude commented 2026-06-28 17:12:31 +00:00
Collaborator
Copy Link

Type: HITL
Parent PRD: docs/prd/chunk-3-skills-library.md

What to build

The 4 deploy phase skills. All are new. Authored via write-skill (0018), evals via write-eval (0017).

Skills and trigger descriptions:

Flat name Trigger description
write-ci-pipeline Write CI pipeline, create Gitea Actions workflow
write-deployment-config Write deployment config, Docker Compose, K8s manifest
write-ai-review-workflow Create AI review workflow, automated PR review
deployment-checklist Pre-deployment checklist, ready to deploy, deployment validation

Key constraints per skill:

  • write-ci-pipeline: targets Gitea Actions YAML; includes secret scan, dependency scan, licence scan, test, and build steps by default
  • write-deployment-config: pinned image/provider versions; resource limits on all K8s resources; no hardcoded secrets; secrets via env vars
  • write-ai-review-workflow: calls AI API via script; posts findings via Gitea API; never auto-merges; human remains in the loop
  • deployment-checklist: validates — linked issue exists and is closed or in-progress; secrets scan clean; dependency scan clean; licence scan clean; tests passing; rollback plan documented; docs/spec/ updated if behaviour changed; which reviewer roles (Architect, Reviewer, Security) have been invoked on this change

Implementation notes

Follow the per-skill workflow defined in docs/notes/skill-implementation-workflow.md.

Known upstream sources to review:

  • bmad-method/bmad-method — BMAD ops/deploy patterns and deployment checklist approach
  • Search GitHub for open-source Gitea Actions skill examples
  • Gitea Actions documentation (Gitea-specific CI syntax differences from GitHub Actions)

Acceptance criteria

  • All 4 SKILL.md files exist at .agents/skills/<skill-name>/SKILL.md; metadata.category: deploy; authoring standard met
  • deployment-checklist includes all listed validation checks, including reviewer role invocation check
  • write-ai-review-workflow includes explicit constraint that it never auto-merges
  • source: fields populated for any adopted upstream content
  • Each skill has a co-located eval at .agents/evals/deploy/<skill-name>/eval.yaml via write-eval
  • install.sh deploys all 4 to ~/.agents/skills/
  • HITL: human runs behavioral test per skill
  • HITL: human reviews each SKILL.md and eval before committing
  • Per-skill process followed for all 4 skills: source discovery → source review → conflict check → synthesis grill → co-write iteratively
  • Trigger description for each skill tested against explicit, implicit, and negative queries before body written
  • eval.yaml for each skill contains all 5 required test types
  • Body ≤500 lines for each skill
  • docs/spec/overview.md updated to reflect all 4 skills deployed

Blocked by

  • 0016 (per-skill workflow)
  • 0017 (write-eval)
  • 0018 (write-skill)
**Type:** HITL **Parent PRD:** `docs/prd/chunk-3-skills-library.md` ## What to build The 4 deploy phase skills. All are new. Authored via `write-skill` (0018), evals via `write-eval` (0017). **Skills and trigger descriptions:** | Flat name | Trigger description | |---|---| | `write-ci-pipeline` | Write CI pipeline, create Gitea Actions workflow | | `write-deployment-config` | Write deployment config, Docker Compose, K8s manifest | | `write-ai-review-workflow` | Create AI review workflow, automated PR review | | `deployment-checklist` | Pre-deployment checklist, ready to deploy, deployment validation | **Key constraints per skill:** - `write-ci-pipeline`: targets Gitea Actions YAML; includes secret scan, dependency scan, licence scan, test, and build steps by default - `write-deployment-config`: pinned image/provider versions; resource limits on all K8s resources; no hardcoded secrets; secrets via env vars - `write-ai-review-workflow`: calls AI API via script; posts findings via Gitea API; never auto-merges; human remains in the loop - `deployment-checklist`: validates — linked issue exists and is closed or in-progress; secrets scan clean; dependency scan clean; licence scan clean; tests passing; rollback plan documented; `docs/spec/` updated if behaviour changed; which reviewer roles (Architect, Reviewer, Security) have been invoked on this change ## Implementation notes Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`. **Known upstream sources to review:** - `bmad-method/bmad-method` — BMAD ops/deploy patterns and deployment checklist approach - Search GitHub for open-source Gitea Actions skill examples - Gitea Actions documentation (Gitea-specific CI syntax differences from GitHub Actions) ## Acceptance criteria - [ ] All 4 SKILL.md files exist at `.agents/skills/<skill-name>/SKILL.md`; `metadata.category: deploy`; authoring standard met - [ ] `deployment-checklist` includes all listed validation checks, including reviewer role invocation check - [ ] `write-ai-review-workflow` includes explicit constraint that it never auto-merges - [ ] `source:` fields populated for any adopted upstream content - [ ] Each skill has a co-located eval at `.agents/evals/deploy/<skill-name>/eval.yaml` via `write-eval` - [ ] `install.sh` deploys all 4 to `~/.agents/skills/` - [ ] **HITL:** human runs behavioral test per skill - [ ] **HITL:** human reviews each SKILL.md and eval before committing - [ ] Per-skill process followed for all 4 skills: source discovery → source review → conflict check → synthesis grill → co-write iteratively - [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written - [ ] eval.yaml for each skill contains all 5 required test types - [ ] Body ≤500 lines for each skill - [ ] `docs/spec/overview.md` updated to reflect all 4 skills deployed ## Blocked by - 0016 (per-skill workflow) - 0017 (`write-eval`) - 0018 (`write-skill`)
Claude added this to the Legacy / Triage milestone 2026-06-28 17:12:31 +00:00
Claude added the Kind/Feature
Priority
Medium
3
 labels 2026-06-28 17:12:31 +00:00
Claude modified the milestone from Legacy / Triage to Skills & Agents 2026-06-28 19:26:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Feature
Priority
Medium
3
Milestone
No items
No Milestone Skills & Agents
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#43
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?