Skip to content

feat(skill-maker,rhdh-jira): hard-require grilling and fix customer field guidance - #77

Open
schultzp2020 wants to merge 3 commits into
mainfrom
feat/grilling-prereq-and-jira-customer-fields
Open

feat(skill-maker,rhdh-jira): hard-require grilling and fix customer field guidance#77
schultzp2020 wants to merge 3 commits into
mainfrom
feat/grilling-prereq-and-jira-customer-fields

Conversation

@schultzp2020

Copy link
Copy Markdown
Collaborator

Summary

  • Hard-require Matt Pocock's grilling skill on skill-maker create/interview and rhdh-jira create paths (to-feature / to-epic / to-issue), with setup detect + confirm/install dialogue; cadence via invoking grilling, domain questions stay local.
  • Encode RHDHPLAN-1661 feedback: no customer names in unprotected fields; prefer a single RHDH-Customer label (authoritative in fields.md, enforced on create/grill).
  • Restructure skill-maker (audit/create disclosed to refs, skill-quality.md, rewritten description) and document the grilling prereq + full Matt pack recommendation in the README.
  • Fix Windows pre-commit pytest for base-images shell scripts (run via bash).

Test plan

  • uv run pytest tests/unit/test_skill_maker_grilling_setup.py tests/unit/test_rhdh_jira_grilling_setup.py tests/unit/test_base_images_and_rpms.py
  • Pre-commit hooks (incl. full pytest) pass on commit
  • Manual: create path with grilling missing → confirm install → re-check → one grill invoke
  • Manual: to-feature with customer context → support key + RHDH-Customer label, no customer name in summary/description

…ield guidance

Create/interview paths gate on Matt Pocock's grilling skill with setup checks,
invoke it for cadence, and keep domain questions local. rhdh-jira encodes
customer-identity and RHDH-Customer label rules from RHDHPLAN-1661 feedback;
skill-maker discloses audit/create branches and adds skill-quality guidance.

Also run base-images shell tests via bash on Windows so pre-commit pytest passes.
Add a local work-breakdown reference (synthesize-then-gap-fill, tracer
bullets, blocking edges, quiz before create) and wire it into Feature/Epic
decomposition — inspiration only, no hard dep on Matt's skills.
Keep tracer-bullet / synthesize guidance; remove references to upstream
skill names so the reference stands alone.
@mattreid

Copy link
Copy Markdown

@schultzp2020 I'm not a skill expert yet, but the updated guidance looks like it should address those two points, thanks for wrapping that in.

Did you try running the revised logic or audit against RHDHPLAN-1661 to see if it would handle the Customer Considerations section differently now (or flag that a name was included)? Have you seen it successfully manipulate security level before? It's not very specific here, but as long as it reliably picks "Red Hat Employee" when trying to restrict visibility, we should be good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants