Skip to content

A reusable workflow that implements an issue: Claude Code Action on the Max token, pull request left to the maintainer to approve #1999

Closed

Description

@fametrano

Decided by the maintainer on 2026-11-02: an issue opened by a member or collaborator, or labelled agent by a maintainer, is implemented by a cloud agent that opens the pull request; approval and release stay human. The Claude Code Action already runs the review on the organization's CLAUDE_CODE_OAUTH_TOKEN (Max subscription, no API billing); it supports issue and label triggers and use_commit_signing: true, which yields GitHub-verified commits as the App.

Add reusable-claude-implement.yml next to reusable-claude-review.yml (same pins, auth, sandboxed tools and budget caps: --max-turns, a job timeout, concurrency per issue) and a thin claude-implement.yml caller, first on one repository for ten issues before alignment rolls it out. The first test settles whether the Action opens the pull request itself or only pushes the claude/ branch, on which its docs disagree. Add the agent label to labels.yml.

Activity

  1. fametrano commented on Nov 2, 2026

    @fametrano
    MemberAuthor

    The maintainer decided on 2026-11-02 that every issue gets an automatic assessment before any implementation, and that the implementation starts by itself only where the assessment recommends it and the author is a member. The assessment is a comment on the issue in the shape the process gives a decision: the problem restated, its Done when and central measurement, the impact, the estimated cost as a diff balance and the complexity it adds, the alternatives with their costs, and warnings on security, API and compatibility. It closes on one of three recommendations: implement, do not implement, or a decision reserved for the maintainer. Where it recommends either of the last two, the workflow adds the decision label and waits for the maintainer's answer. Starting points are claude-code-action's examples/issue-triage.yml and CodeRabbit's Issue Planner (@coderabbitai plan), which the Open Source plan includes. The assessment job is read-only. The implement job runs after it, in the same reusable workflow.

  2. fametrano commented on Nov 2, 2026

    @fametrano
    MemberAuthor

    Claimed by a session on 2026-11-02 (fametrano).

  3. 45 remaining items

  4. fametrano commented on Nov 9, 2026

    @fametrano
    MemberAuthor

    Trial status, 2026-11-09:

  5. fametrano commented on Nov 10, 2026

    @fametrano
    MemberAuthor

    Trial status, 2026-11-10.

    v2026.11.11 (5be973d, #2141) is tagged; ai-agents-process (#365, #366) and portanode (#856, #857) pin it.

    The six issues were relabelled agent. Five pull requests opened in btclib-org/portanode, and all five landed:

    PR closes landed as
    btclib-org/portanode#858 #746 written by the agent
    btclib-org/portanode#860 #686 written by the agent
    btclib-org/portanode#859 #669 plus one commit: the new test could not see a leftover rcfile on macOS, where mktemp -t ignores TMPDIR
    btclib-org/portanode#861 #691 plus one commit: the Blinter baseline was not re-keyed, so the required Script security check failed
    btclib-org/portanode#862 #675 plus one commit: a comment claimed more than the pattern does

    #691, #686 and #675 were opened by a non-member, so the assessment applied decision; an administrator removed it and the edit ran without a second assessment, as designed.

    btclib-org/ai-agents-process#282 opened no pull request: the gates refused the agent's edit on markdownlint MD013 (a 106-column line in skills/btclib-table/SKILL.md), which is the gates doing their job.

    The bip32-descriptors pins wait on btclib-org/bip32-descriptors#139.

  6. fametrano commented on Nov 10, 2026

    @fametrano
    MemberAuthor

    btclib-org/ai-agents-process#282, relabelled once: the second run passed the gates and opened btclib-org/ai-agents-process#367, which landed as the agent wrote it (bd5af12). Six issues, six pull requests landed.

  7. fametrano commented on Nov 10, 2026

    @fametrano
    MemberAuthor

    Done, measured: the six issues of the trial each opened a pull request that landed (table in the comment above, and btclib-org/ai-agents-process#367 for #282). The bip32-descriptors pins (btclib-org/bip32-descriptors#195, #196) continue in that repository's own session; nothing else of this step is open.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions