oncall-seed-metadata

Seeds engineer GitHub username metadata into DynamoDB for deploy gate verification.

1|Updated Feb 16, 2026

Search Tags:#devops #aws #dynamodb #oncall #deploy gate #metadata seeding #github username

Ready to run

npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill oncall-seed-metadata-codepresso-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oncall-seed-metadata
Source: https://github.com/codepresso-dev/codepresso-ai-plugin/tree/main/skills/oncall-seed-metadata
Command: npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill oncall-seed-metadata-codepresso-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The production deploy gate cannot verify who triggered a workflow unless it can map an engineer's display name to their GitHub username. This Skill writes that mapping into the oncall DynamoDB table so deploy verification stops failing with "engineer not found" errors. ## Core Features & Use Cases - Metadata Seeding: Writes `ENGINEER#`-prefixed items (name, GitHub username, email) into the `oncall-assignments-history` DynamoDB table in `ap-northeast-2`. - Existing-State Check: Scans for current metadata first, shows it in a table, and asks for confirmation before updating. - Interactive Roster Collection: Pulls the roster from an untracked local config file or asks the user directly, keeping personal data out of the repository. - Use Case: A new engineer joins the on-call rotation and the deploy gate rejects their workflow triggers. Run this Skill to add their GitHub username mapping, then verify the seeded rows. ## Quick Start Run the oncall-seed-metadata command to add the new engineer's GitHub username mapping to the DynamoDB deploy gate table.

Frequently Asked Questions about oncall-seed-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I seed engineer metadata into DynamoDB for deploy gate verification?▼

Run the oncall-seed-metadata command, which scans the oncall-assignments-history table for existing ENGINEER# items, confirms the roster with you, then writes one put-item per engineer with their name, GitHub username, and email.

Why is the deploy gate failing with engineer not found errors?▼

The deploy gate looks up ENGINEER#-prefixed metadata items in DynamoDB to map display names to GitHub usernames. If an engineer's metadata item is missing, verification fails; seeding their entry resolves it.

Where does the engineer roster come from?▼

The roster is not hardcoded. It is collected interactively via prompts, read from an untracked local file like .codepresso/oncall-roster.json, or pulled from an authoritative source such as an HR system or the GitHub team API.

Will seeding metadata affect the on-call schedule assignments?▼

No. Metadata items use the ENGINEER# prefix on AssignmentDate, while schedule assignments use date-based prefixes like 2026-04-07. The oncall allocator Lambda only touches date-prefixed items and ignores metadata entries.

How do I remove an engineer from the deploy gate metadata?▼

Use aws dynamodb delete-item directly on the engineer's ENGINEER# item in the oncall-assignments-history table. This Skill only handles adding or updating metadata, not removal.