Install Sepo agent infrastructure

AS
2d ago
+62857-0

Summary

Adds the Sepo agent backend to this repository so @sepo-agent can answer, implement, review, and fix work on GitHub. This PR adds agent infrastructure only — no application source, secrets, or branch protection are changed.

Installed from the latest stable Sepo release v0.5.0 (self-evolving/repo).

Required setup after merge

  1. Install the Sepo GitHub App on this repository, or choose another auth path from the setup guide.
  2. Add at least one model-provider secret under Actions secrets: OPENAI_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, and/or ANTHROPIC_API_KEY.
  3. Run the Agent / Onboarding / Check Setup workflow.
  4. Review the Sepo setup check issue it opens and complete any remaining setup it reports.
  5. If agent/memory is missing, run Agent / Memory / Initialization.
  6. Optionally run Agent / Rubrics / Initialization if this repo wants rubric steering.

Also confirm Issues and GitHub Actions are enabled (Settings → General → Features, Settings → Actions → General).

Source revision

  • self-evolving/repo @ v0.5.0 (5f7d2032080e9c0578d0e4cb3b98b2f695f33547)

Installed files

  • .agent/ — agent backend (265 files), excluding generated .agent/dist/ and .agent/node_modules/.
  • .github/ — agent workflows (28), composite actions, prompts, issue templates, and assets, merged into the existing .github/.
  • .gitignore — appended .agent/dist/ and .agent/node_modules/.

Preserved / skipped

  • All target-owned .github/ files preserved; the conflict audit found no source path that collides with an existing target path.
  • Root README.md, AGENTS.md, and .skills/ were not copied (install defaults).
  • No application source changed.

Validation

  • npm ci, npm run build, and npm test pass on the source at v0.5.0 (run once against the identical payload).
  • git diff --cached --check is clean.
  • Conflict audit: no source .github path collides with an existing target path.

Skipped checks

  • Per-repo .agent build/test not rerun; the payload is byte-identical to the validated source revision.

This PR was created by an AI agent (OpenHands) on behalf of @ashcoft.


Devin Review


Summary by cubic

Installs the Sepo agent backend into this repository so @sepo-agent can answer, implement, review, and fix work on GitHub. Adds agent infrastructure from self-evolving/repo v0.5.0 and merges its agent workflows into .github/; no application source, secrets, or branch protection are changed.

Setup required after merge

  • Install the Sepo GitHub App on this repository.
  • Add at least one model-provider secret under Actions secrets: OPENAI_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, or ANTHROPIC_API_KEY.
  • Run the Agent / Onboarding / Check Setup workflow and complete any remaining setup it reports.
  • Run Agent / Memory / Initialization if the agent/memory branch is missing.
  • Confirm Issues and GitHub Actions are enabled in repository settings.

This change is Reviewable

RetriggerView in GreptileConfidence Score: 2/5

Fix fork PR requests, staged-change checks, and memory scan completion before merging.

Fix All in CodexFindings

  1. P1 Fork PR requests fail ▶
  2. P1 Staged edits skip checks ▶
  3. P1 Unsaved lessons count as saved ▶
Fix with agent prompt
### Issue 1
.github/workflows/agent-entrypoint.yml:12-17
`agent-entrypoint.yml` accepts fork PR bodies, reviews, and inline comments, but GitHub withholds repository secrets from those events. With the documented API-key setup, provider selection fails before Sepo can answer or review-even when the owner sends the request.

Handle these requests through a trusted workflow that receives secrets. Keep its workflow and runtime on the default branch and treat PR content only as input.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

### Issue 2
.agent/scripts/post-agent-verify.sh:18-24
`post-agent-verify.sh` excludes staged changes from both the whitespace check and the changed-file list. If an agent stages edits without committing, `hasChanges()` requests verification, but this script skips the YAML check or TypeScript build for those files. The later commit step publishes them anyway.

Include `git diff --cached --check` and `git diff --cached --name-only` so staged-only edits receive the same checks.

### Issue 3
.github/workflows/agent-memory-scan.yml:132-133
`agent-memory-scan.yml` advances `last_scan_at` when `steps.scan` succeeds, even if its memory push failed. `commit_memory` uses `continue-on-error: true`, so a competing answer or sync push can reject the scan's push while leaving the scan green. The next scheduled scan then skips that activity because it is older than the new cursor, leaving the curated edits unpublished.

Expose the memory commit outcome and require successful persistence before advancing the cursor. A successful run with no changes should still count.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Installs Sepo's runtime, documentation, shared actions, and GitHub workflows without changing application source.

Three issues need fixes:

  • GitHub requests now reach Sepo through mentions and agent labels.
  • Sepo keeps its long-term project notes on an agent memory branch.
  • Sepo uses a separate rubrics branch for team preferences.
  • Sepo can hand off work and run scheduled repository tasks.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[GitHub mention or label] --> B[Router]
  B --> C[Choose route and check access]
  C --> D[Answer or review]
  C --> E[Implement or fix PR]
  E --> F[Verify edits]
  F --> G[Commit and publish]
  D --> H[Save memory]
  E --> H
  I[Scheduled memory scan] --> H
  H --> J[Record scan completion]

Reviews (1) · Last reviewed commit: "chore: install Sepo agent infrastructure" · Reviewed by Greptile