بنقرة واحدة
session-hardener
Explicit post-session repo hardening review for OpenCode coding sessions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Explicit post-session repo hardening review for OpenCode coding sessions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze Codex session history since the last successful coaching run and return exactly five practical workflow improvements. Use when the user explicitly invokes the AI session coach or asks to review recent Codex sessions for recurring friction, instruction gaps, or reusable workflow improvements.
Code immersion: walks the user through how a project, component, or feature works, step by step. Use when the user wants to understand how code works or asks for a walkthrough.
Capture, update, or organize a task in Singularity. Use when the user wants to add a task, todo, reminder, deadline, or scheduled work item.
Draft, group, or create Conventional Commits. Use when the user asks for a commit message, commit title/body, a local commit from staged changes, categorizing local changes, partial staging mixed work, multiple semantic commits, or remaining artifacts.
Explicit workflow coach for analyzing unarchived OpenCode sessions.
Explicit plan and design stress-test interview.
| name | session-hardener |
| description | Explicit post-session repo hardening review for OpenCode coding sessions. |
| disable-model-invocation | true |
Turn the current OpenCode coding session into exactly 3 durable repo-hardening recommendations. Recommend only; do not edit, stage, commit, or apply fixes unless the user separately asks for implementation.
Inspect the current repository before judging the session:
AGENTS.md.git status --short,
git diff --stat, and focused diffs for touched files.Completion criterion: repo evidence covers the files or workflows that the session changed or struggled with.
Collect current session evidence:
scripts/collect_current_session.py --session-id <current_session_id> --pretty
using the session ID from conversation context.scripts/collect_current_session.py --latest-for-cwd . --pretty and label
it "latest session for cwd".Look for repo-hardening problems, not code-review nits:
AGENTS.md rulesPick exactly 3 problems by recurrence risk and usefulness of a durable repo update. Prefer actionable repo changes over process advice.
Completion criterion: each selected problem has objective evidence and at least one concrete repository-level fix.
Return the response contract below. Do not include patches.
[AGENTS.md](/absolute/path/AGENTS.md:12).medium or low.Return exactly 3 numbered problems:
1. **Problem:** Paragraph explaining the recurring risk and why it matters.
**Evidence:** Paragraph with short dialogue/tool quote or repo file link.
**Fix 1:** Paragraph describing one durable repo update.
**Fix 2:** Optional paragraph for a meaningful alternative or complement.
**Confidence:** high|medium|low.
Run from this skill directory or pass the full path:
python3 config/opencode/skills/session-hardener/scripts/collect_current_session.py --session-id <id> --pretty
Useful options: --session-id, --latest-for-cwd, --opencode-home,
--max-message-chars, --max-output-chars, and --max-events.
The script is read-only with respect to OpenCode state, log files, and repository files. It must not update the database, modify logs, or write generated artifacts.