rhdh-test-plan-review

Name: rhdh-test-plan-review
Author: redhat-developer

15stars31forks

How to install rhdh-test-plan-review?

redhat-developer/rhdh-skill/rhdh-test-plan-review

$npx -y skills add redhat-developer/rhdh-skill --skill rhdh-test-plan-review

Installs into the current project.

Summary

Reviews an RHDH test plan Jira ticket and suggests platform/integration version updates based on support lifecycle pages and RHDH release milestones. Use when given an RHDH test plan Jira ticket ID to check which platform/integration versions to add or remove. Use when asked to "

Files · 1

View on GitHub

SKILL.md

1	<essential_principles>
2
3	<principle name="no_changes_without_approval">
4	Never modify Jira tickets without explicit user approval. Collect all decisions first, summarize them, then ask whether to apply — direct update [d], comment [c], or discard [n].
5	</principle>
6
7	<principle name="version_tracking_rules">
8	Different platforms accumulate versions differently:
9	- OCP: accumulate all active versions
10	- AKS, EKS, GKE, Quay: single latest version only — replace, never accumulate
11	- ARO, OSD, ROSA: single version each, evaluated independently — replace if a newer version is GA before code_freeze
12	- RHBK: track major versions only (e.g., `26` not `26.0`); accumulate all active majors
13	- PostgreSQL: RHDH support policy is the baseline; Backstage-only versions require a Jira Feature ticket warning
14	</principle>
15
16	<principle name="milestone_cutoffs">
17	Add/remove decisions are based on `code_freeze` and `ga_date` from the RHDH schedule sheet — not today's date.
18	- Add: version GA date ≤ `code_freeze`
19	- Remove: version EOL date ≤ `ga_date`
20	</principle>
21
22	<principle name="adf_preservation">
23	Jira descriptions are ADF (nested JSON). When updating, modify only version strings and date cells inside existing table cells — never convert to plain text and back. Preserve all other ADF structure exactly.
24	</principle>
25
26	<principle name="token_safety">
27	Never read `.jira-token` into context. Always use shell substitution: `"$(cat "$TOKEN_FILE")"`.
28	</principle>
29
30	</essential_principles>
31
32	<intake>
33
34	## RHDH Test Plan Review
35
36	Provide a Jira ticket ID or URL (e.g., `RHIDP-8994`) to begin.
37
38	Wait for response before proceeding.
39
40	</intake>
41
42	<routing>
43
44	\| Input \| Workflow \|
45	\|-------\|----------\|
46	\| Jira ticket ID or URL \| Read `workflows/review-test-plan.md` and follow it \|
47
48	</routing>
49
50	<reference_index>
51
52	\| Reference \| Purpose \| Path \|
53	\|-----------\|---------\|------\|
54	\| sources \| Lifecycle URLs and extraction guidance per platform/integration \| `references/sources.md` \|
55	\| google-sheets-setup \| One-time gcloud auth setup for schedule sheet access \| `references/google-sheets-setup.md` \|
56	\| rhdh-jira auth \| Jira REST API token setup and curl patterns \| `../rhdh-jira/references/auth.md` \|
57
58	</reference_index>
59
60	<success_criteria>
61
62	- [ ] RHDH version extracted from ticket
63	- [ ] Milestone dates fetched from schedule sheet
64	- [ ] All platform and integration versions checked against lifecycle sources
65	- [ ] Overview diff presented (key dates, platforms, integrations)
66	- [ ] Each proposed change reviewed interactively (a/k/e)
67	- [ ] User chose how to apply: [d] direct update, [c] comment, [n] discard
68	- [ ] If [d]: Jira description updated via REST API; child tasks offered one at a time
69	- [ ] If [c]: comment posted to ticket
70	- [ ] If [n]: confirmed no changes were made
71
72	</success_criteria>

People who liked this also viewed

6 picks

Type

rhdh-test-plan-review

15stars31forks

View on GitHub

How to install rhdh-test-plan-review?

redhat-developer/rhdh-skill/rhdh-test-plan-review

$npx -y skills add redhat-developer/rhdh-skill --skill rhdh-test-plan-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<essential_principles>
2
3	<principle name="no_changes_without_approval">
4	Never modify Jira tickets without explicit user approval. Collect all decisions first, summarize them, then ask whether to apply — direct update [d], comment [c], or discard [n].
5	</principle>
6
7	<principle name="version_tracking_rules">
8	Different platforms accumulate versions differently:
9	- OCP: accumulate all active versions
10	- AKS, EKS, GKE, Quay: single latest version only — replace, never accumulate
11	- ARO, OSD, ROSA: single version each, evaluated independently — replace if a newer version is GA before code_freeze
12	- RHBK: track major versions only (e.g., `26` not `26.0`); accumulate all active majors
13	- PostgreSQL: RHDH support policy is the baseline; Backstage-only versions require a Jira Feature ticket warning
14	</principle>
15
16	<principle name="milestone_cutoffs">
17	Add/remove decisions are based on `code_freeze` and `ga_date` from the RHDH schedule sheet — not today's date.
18	- Add: version GA date ≤ `code_freeze`
19	- Remove: version EOL date ≤ `ga_date`
20	</principle>
21
22	<principle name="adf_preservation">
23	Jira descriptions are ADF (nested JSON). When updating, modify only version strings and date cells inside existing table cells — never convert to plain text and back. Preserve all other ADF structure exactly.
24	</principle>
25
26	<principle name="token_safety">
27	Never read `.jira-token` into context. Always use shell substitution: `"$(cat "$TOKEN_FILE")"`.
28	</principle>
29
30	</essential_principles>
31
32	<intake>
33
34	## RHDH Test Plan Review
35
36	Provide a Jira ticket ID or URL (e.g., `RHIDP-8994`) to begin.
37
38	Wait for response before proceeding.
39
40	</intake>
41
42	<routing>
43
44	\| Input \| Workflow \|
45	\|-------\|----------\|
46	\| Jira ticket ID or URL \| Read `workflows/review-test-plan.md` and follow it \|
47
48	</routing>
49
50	<reference_index>
51
52	\| Reference \| Purpose \| Path \|
53	\|-----------\|---------\|------\|
54	\| sources \| Lifecycle URLs and extraction guidance per platform/integration \| `references/sources.md` \|
55	\| google-sheets-setup \| One-time gcloud auth setup for schedule sheet access \| `references/google-sheets-setup.md` \|
56	\| rhdh-jira auth \| Jira REST API token setup and curl patterns \| `../rhdh-jira/references/auth.md` \|
57
58	</reference_index>
59
60	<success_criteria>
61
62	- [ ] RHDH version extracted from ticket
63	- [ ] Milestone dates fetched from schedule sheet
64	- [ ] All platform and integration versions checked against lifecycle sources
65	- [ ] Overview diff presented (key dates, platforms, integrations)
66	- [ ] Each proposed change reviewed interactively (a/k/e)
67	- [ ] User chose how to apply: [d] direct update, [c] comment, [n] discard
68	- [ ] If [d]: Jira description updated via REST API; child tasks offered one at a time
69	- [ ] If [c]: comment posted to ticket
70	- [ ] If [n]: confirmed no changes were made
71
72	</success_criteria>

People who liked this also viewed

6 picks

Type