docs(feat): add GitHub pipeline skills#23
Open
Ducksss wants to merge 4 commits into
Open
Conversation
Summary: - Refresh P0 follow-up rows from the July 6 Airtable reconciliation. - Record the merged ishandutta listing and Unikorn maintenance recheck. - Add the compact monthly reconciliation note for Airtable updates. Rationale: - Airtable is the durable outreach ledger, but LAUNCH.md still needs a short handoff summary for future agents. - No new outreach was opened because the open-PR gate remains active and the top startup-profile candidates require unsupported company or geography claims. Tests: - git diff --check
Summary: - Add Airtable-first lead qualification rules to the outreach agent. - Document the July 6 Airtable cleanup in LAUNCH.md. - Add a regression test for the outreach agent instructions. Rationale: - Outreach should qualify ICP fit before drafting or submitting anything. - codex-profiles is a developer CLI tool, not a startup profile. - Startup, venture, regional, and generic launch surfaces need a hard truthfulness gate to avoid forced or unsupported claims. Tests: - node test/outreach-agent-test.mjs - git diff --check - make test - make lint
Summary: - Add repo-local GitHub lead gen, qualification, closing draft, and monitoring skills. - Route outreach automation through phase-specific skills with Airtable handoffs. - Add regression coverage for skill boundaries and agent routing. Rationale: - Split the GitHub lead workflow into small context-safe phases. - Keep Airtable as the durable handoff and preserve approval-gated external outreach. Tests: - make test - make lint - git diff --check - quick_validate.py for all four skills - plugin-eval analyze for all four skills: 100/100, 0 fail, 0 warn
Summary: - Record the 2026-07-08 issue-first outreach wave in LAUNCH.md. - Capture the submitted issue URLs, monitoring next actions, and the one immediate out-of-scope decline. Rationale: - Airtable remains the durable outreach ledger, while LAUNCH.md provides a compact handoff for follow-up monitoring. - Recording the approved wave keeps future agents from duplicating outreach or opening PRs before maintainers confirm scope. Tests: - git diff --check - Airtable readback for 20 target rows and matching closing logs - GitHub direct issue verification for 20 submitted issue URLs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
agent.mdthrough phase-specific skills with Airtable as the durable handoff.Rationale
Verification
make testmake lintgit diff --checkquick_validate.pyfor all four skillsplugin-eval analyzefor all four skills: 100/100, 0 fail, 0 warnExternal outreach remains approval-gated by the skills; they may draft artifacts, but they do not submit PRs, issues, comments, emails, or other external communications without explicit approval.