skills.rest
divalto
divaltoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pushing-retex-to-github

Pushes RETEX journal entries to GitHub as labeled issues via gh CLI.

6|Updated May 11, 2026
Search Tags:#github#idempotent#gh cli#issue automation#markdown parsing#feedback sync#retex
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill pushing-retex-to-github-divalto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pushing-retex-to-github
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/pushing-retex-to-github
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill pushing-retex-to-github-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Field feedback logged in a local RETEX-skills.md file stays invisible to the central team. This Skill automatically synchronizes R-NNN feedback entries to a shared GitHub repository as issues, without manual copy-pasting, and without ever losing local data. ## Core Features & Use Cases - Automatic sync via hook: after each edit of RETEX-skills.md, new or modified R-NNN entries are parsed and pushed as GitHub issues using gh issue create. - Idempotent tracking: a local .retex-pushed.json cache stores issue numbers and content hashes, so unchanged entries are skipped and modified entries become comments on the existing issue instead of duplicates. - Label derivation and degraded mode: category and severity fields map to GitHub labels, and if gh is missing or unauthenticated the push logs the failure and exits without blocking the edit. - Use Case: A partner consultant writes a bug report entry R-028 in their RETEX journal; the skill creates issue [R-028] ... on divalto/divalto-ia-devkit with labels retex, bug-skill, and severite:haute. ## Quick Start Ask the AI to configure the target GitHub repository for this workspace's RETEX file and then push all new entries from RETEX-skills.md to GitHub.

Frequently Asked Questions about pushing-retex-to-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push RETEX entries to GitHub issues automatically?▼

Run init_config.py once with your RETEX file path and target repo, then push_new_entries.py parses new R-NNN entries and creates one GitHub issue per entry via gh issue create. A PostToolUse hook can also trigger the push automatically after each edit of RETEX-skills.md.

How do I configure the target GitHub repository for RETEX sync?▼

Run init_config.py with --retex-file and --repo owner/name to create .retex-github.json with the repo and label mappings. Existing entries are marked as already pushed to avoid accidental backfill, and --global writes a shared config in ~/.claude/.

What happens if GitHub CLI is not installed or not authenticated?▼

The push runs in degraded mode: it logs 'gh CLI absent' or 'gh non authentifie' to .retex-push.log and exits with code 0 without blocking the edit. No issue is created, but the RETEX entries remain in the local file for a later push.

Does the skill create duplicate issues when an entry is edited?▼

No. The .retex-pushed.json tracking file stores each entry's issue number and SHA-1 content hash. Unchanged entries are skipped, and modified entries are added as comments on the existing linked issue instead of creating duplicates.

Why is my RETEX entry not appearing as a GitHub issue?▼

Check that .retex-github.json exists locally or in ~/.claude/, since an unconfigured push aborts silently. Also check .retex-push.log for WARN parsing lines: headers missing the '-- YYYY-MM-DD --' date are rejected, and entries inside HTML comments are ignored.

How do I push all existing RETEX entries at once?▼

Use push_new_entries.py with --backfill --yes-i-want-to-push-everything to ignore the tracking cache and push every entry. This guard flag prevents accidental mass issue creation on historical RETEX files.

Related Skills

Explore More Software Engineering Skills→
DozyboyDozyboy

hs:journal

Write honest technical journal entries recording decisions, failures, and lessons learned after sessions.

Community
Intermediate
Aum08DesaiAum08Desai

github-issues

Manage GitHub issues via gh CLI or REST API.

Community
Intermediate
shidax-corpshidax-corp

Create GitHub Issues and Pull Requests

Create and manage GitHub Issues and Pull Requests via the GitHub CLI.

Official
Intermediate
jordanfbrownjordanfbrown

create-pull-request

Create a draft GitHub pull request with Jira ticket context.

Community
Advanced