Local repository insights

Show the user what their own repositories say about how they work, read from git on this machine with no GitHub token and no network, then offer the next step. This often runs in a user's first session, after GitHub could not be used, so it must end with something about their own work, never with only a blocker.

Plan

After reading this skill, use update_plan to create the live Local Insights plan from the four numbered workflow headings below. Mark a step in_progress or completed in the same response as that step's tool call. Mark step 1 with verifies: true and step 2 with deliverable: true in every update_plan call: step 2's work is the reply itself.

• Step 1. Read the local repositories with analyze_local_repositories.
• Step 2. Show the local insights report as a text-only reply.
• Step 3. Use ask_user_choice to ask what to watch and what comes next.
• Step 4. Save what to watch with memory_remember and start the chosen next step.

Workflow

1. Read the local repositories

Call analyze_local_repositories with:

• reason:
  • github_not_connected when the user chose their local repositories at the GitHub setup menu, or GitHub has no token;
  • github_failed when analyze_github_ci_reliability could not read GitHub; pass its error_kind as github_error when it named one;
  • no_github_actions when the user picked a repository marked (local insights);
  • requested otherwise.
• repository: the repository the user picked earlier in this session, as owner/repo or its local path, if any.
• paths: the path of each repository in this session's scan_local_git_workspace result, the picked repository's own path first, then the most active ones, when a scan ran. Omit it otherwise; the tool scans.

Complete when analyze_local_repositories has returned in this turn. If it returned cancelled, stop. If it returned success: false with an error, say in one line that the local repositories could not be read, and stop. If this build has no analyze_local_repositories tool, say in one line that opensre update adds this report, and stop.

2. Show the report

Reply with the report below as Markdown text and nothing else; call no tool in that message. The host shows it, then the plan continues with step 3.

Every number comes from the tool result: never estimate, round, or add one. The tool returns no commit messages or code, so never quote any.

1. When reason is github_not_connected or github_failed, open with one line that names the blocker in plain words and says this report needs no GitHub, for example: "GitHub couldn't be read from this machine, so here's what your local history shows instead." Nothing more about the blocker.
2. One line: <repositories> repositories · <own_commits> commits by you in the last <days> days. Read from git on this machine; no code or commit messages left it.
3. A What stands out heading, then the first three insights whose label is not Rhythm, in the order given. Each is one bullet: the label in bold with a colon, the fact unchanged, then one short clause from the table below.
4. When a Rhythm insight is present, one line after the bullets: its fact.
5. When reason is not requested, one line: Connect GitHub to add: and the github_only_metrics joined with ·.
6. Each coverage_notices entry on its own line.

When repositories is 0, replace items 2 to 6 with one line saying no local repositories with commits in that window were found, and, when skipped_protected lists folders, that those folders were not searched.

Complete when the reply containing the report has been shown.

3. Ask what to watch and what comes next

Call ask_user_choice once with two questions:

1. label Watch, title Which of these should OpenSRE keep an eye on?, multi_select true, options: the labels of the insights shown under What stands out in step 2, then None of these.
2. label Next, title What next?, options from the first row that applies, then Not now:

When step 2 showed nothing under What stands out (for example repositories is 0), ask only the Next question, as title and options. End the turn after the call. If the result says the menu is unavailable, list the questions with numbered options as text and wait.

Complete when the ask_user_choice call has returned in this turn. The answers arrive as the next user message.

4. Remember and start the next step

When the Watch answer names insights, call memory_remember with name local-insights-watch, type preference, a one-line description, and content listing the chosen labels and today's date, in the same response as the next action below.

Then act on the Next answer:

• Connect GitHub and get the CI report, Try the CI report again, Pick another repository, or Get the CI report for one of these repositories: call skill_view(name="analyzing-github-ci-performance") and follow it.
• Reconnect GitHub: call slash_invoke with command /integrations and args ["setup", "github"], then end the turn.
• Show me how to update OpenSRE: reply in one line that opensre update installs the latest build, and to ask again afterwards.
• Watch OpenSRE fix a failing check in a demo repo (under 5 min): call skill_view(name="scheduling-github-ci-repairs") and follow it.
• Look in <folder>: call analyze_local_repositories again with root set to that folder and the same reason, then repeat steps 2 and 3.
• Not now: acknowledge in one line and conclude.

Complete when the chosen next step has started or the user declined.