Agent skill

Issue Doc Sync

by kxn in kxn/codex-remote-feishu

A skill your agent uses when syncing closed GitHub issues back into repo docs.

No licenceAuto-check passed

Install Issue Doc Sync

skills CLI
$ npx skills add kxn/codex-remote-feishu --skill issue-doc-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kxn/codex-remote-feishu issue-doc-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kxn/codex-remote-feishu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/issue-doc-sync .claude/skills/issue-doc-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-doc-sync
GitHub stars
328
Token cost
~932 tokens
SKILL.md length
440 words
Files
2 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when syncing closed GitHub issues back into repo docs.

  • Works in 6 steps: Sync the current branch first. → List only changed closed issues. → Review each candidate issue. → …
  • Syncing closed GitHub issues back into repo docs
  • SKILL.md covers Workflow, Decision Rules, State Cache and References
  • Calls git and rg

What it does

Issue Doc Sync is an agent skill from kxn/codex-remote-feishu. Use when syncing closed GitHub issues back into repo docs. Scans closed issues incrementally by updatedAt, reuses a tracked state cache, surfaces only candidates that changed since the last extraction, and records skip/merge/new-doc decisions for this repository.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/doc-template.md`).

It works with GitHub. The repository describes itself as: Yet another codex remote in feishu.

When your agent uses it

  • Syncing closed GitHub issues back into repo docs

Example prompts

  • “/issue-doc-sync”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Sync the current branch first.
  2. List only changed closed issues.
  3. Review each candidate issue.
  4. Update docs.
  5. Record the decision in the tracked state cache.
  6. Validate.

What it can do on your machine

Read from SKILL.md and the folder at commit 4522572. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issue Doc Sync loads about 932 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~932
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 440 words (~932 tokens).

“Use this skill when the user asks to:”

— opening of SKILL.md by kxn
name
issue-doc-sync

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .codex/skills/issue-doc-sync of kxn/codex-remote-feishu.

  • SKILL.md
  • references/doc-template.md

Open the folder on GitHubat commit 4522572

Compare with similar skills

Issue Doc Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Doc Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Doc Sync this skillkxn/codex-remote-feishu328—~932Automated safety check: PassNone
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.8k tokensUpdated today
    Research & ScienceAuto-check: notes

More from kxn/codex-remote-feishu

All 9 skills in this repo
  • Issue Workflow Guardrail

    kxn/codex-remote-feishu

    A skill your agent uses when handling a GitHub issue in this repository: raw issue shaping, implementability reassessment, fast/full classification, parent/child orchestration, execution snapshots…

    328 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Local Upgrade

    kxn/codex-remote-feishu

    A skill your agent uses when the user asks for this repository's local upgrade flow: 本地升级, 拉最新代码后升级本地 daemon, upgrade-local.sh, or triggering the built-in local upgrade transaction from a repo build.

    328 GitHub stars~951 tokensUpdated 7 days ago
    Auto-check passed
  • Safe Push

    kxn/codex-remote-feishu

    A skill your agent uses when pushing committed changes from this repository, especially when git push may fail because the remote branch advanced.

    328 GitHub stars~639 tokensUpdated 7 days ago
    Auto-check passed
  • Relay Stack Playbook

    kxn/codex-remote-feishu

    A skill your agent uses when working on this repository's relay stack: Codex app-server protocol translation, relayd, relay-wrapper, Feishu bot integration, VS Code remote integration, or real-stack…

    328 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Build Page Mock

    kxn/codex-remote-feishu

    A skill your agent uses when creating or revising a page mock, browser-runnable prototype, or interactive demo for this repository's web, setup, onboarding, status, or admin pages, and also when…

    328 GitHub stars~1.7k tokensUpdated 7 days ago
    Auto-check passed
  • Feishu UI State Machine Guardrail

    kxn/codex-remote-feishu

    Audit and update this repository's canonical Feishu card UI state machine after changing Feishu card state-machine logic carriers such as callback schema/parsing, card action routing, inline replace…

    328 GitHub stars~1.2k tokensUpdated 7 days ago
    Auto-check passed

Works with

Questions about Issue Doc Sync

What does Issue Doc Sync do?

A skill your agent uses when syncing closed GitHub issues back into repo docs. Issue Doc Sync is an agent skill from kxn/codex-remote-feishu. Use when syncing closed GitHub issues back into repo docs.

When should I use Issue Doc Sync?

Issue Doc Sync fits situations like: syncing closed GitHub issues back into repo docs.

How do I install Issue Doc Sync in Claude Code?

Run `npx skills add kxn/codex-remote-feishu --skill issue-doc-sync -a claude-code`. Or copy the skill folder (.codex/skills/issue-doc-sync in kxn/codex-remote-feishu) into .claude/skills/issue-doc-sync in your project. Claude Code loads it when a task matches its description.

How do I install Issue Doc Sync in Codex?

Run `npx skills add kxn/codex-remote-feishu --skill issue-doc-sync -a codex`. Or copy the skill folder (.codex/skills/issue-doc-sync in kxn/codex-remote-feishu) into .agents/skills/issue-doc-sync in your project. Codex loads it when a task matches its description.

Can I use Issue Doc Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kxn/codex-remote-feishu --skill issue-doc-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-doc-sync, .gemini/skills/issue-doc-sync, .github/skills/issue-doc-sync and .opencode/skills/issue-doc-sync in your project.

What does Issue Doc Sync need to run?

Going by SKILL.md and its folder, Issue Doc Sync needs the command-line tools its instructions call (git and rg).

Does Issue Doc Sync access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Issue Doc Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Issue Doc Sync use?

No licence was found for Issue Doc Sync or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Issue Doc Sync use?

About 932 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 215 tokens, read only when the agent opens those files.

What are the alternatives to Issue Doc Sync?

Skills that share tags, products or a category with Issue Doc Sync: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Doc Sync?

kxn (a GitHub user) maintains it in kxn/codex-remote-feishu, which has 328 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.

Source: kxn/codex-remote-feishu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.