Run any Skill in Manus with one click

sync-upstream-radius

Stars672

Forks298

UpdatedJune 8, 2026 at 07:55

Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Use when a check finds new upstream commits, a protocol-library defect is suspected, or for routine dependency maintenance.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

talkincode

talkincode/toughradius

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	sync-upstream-radius
description	Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Use when a check finds new upstream commits, a protocol-library defect is suspected, or for routine dependency maintenance.

Skill: Track & Sync the Upstream RADIUS Library

Feature IDs: TR-F021 / TR-F022 | Milestone: M7

Background

Core protocol library: layeh.com/radius (original repo https://github.com/layeh/radius).
Org fork: github.com/talkincode/radius (https://github.com/talkincode/radius).
Wiring: in go.mod
```
require layeh.com/radius v0.0.0-<pseudo>
replace layeh.com/radius => github.com/talkincode/radius v<tag>
```
i.e. the build actually uses the fork, while the layeh.com/radius import path stays unchanged.

When to use

Routine (weekly recommended) manual check of whether upstream layeh/radius has new commits.
When a protocol codec / attribute-handling / security defect is found or suspected.
During routine dependency maintenance.

Steps

Confirm the currently pinned version
```
grep -E "layeh.com/radius|talkincode/radius" go.mod
```
Record the fork tag the replace points to, and the upstream commit short SHA in the require pseudo-version.
Diff against upstream
- Original repo layeh/radius: review new commits since the pinned commit, e.g. via GitHub compare: https://github.com/layeh/radius/compare/<pinned_sha>...master, or git log <pinned_sha>.. in an upstream clone.
- Focus on: security fixes, attribute codec correctness, EAP / VSA / packet-parsing changes.
Assess the sync
- If an upstream fix is important and the fork lacks it: merge/cherry-pick it into the fork (talkincode/radius) and cut a new tag.
- Update this repo's go.mod replace to the new tag and run go mod tidy.
- If the fix does not affect this project's usage, record the "assessed, sync deferred" rationale (reply in the tracking issue).

Verify

go build ./...
go test ./...
go test -tags=integration -count=1 ./test/integration/...   # needs Postgres, see ../add-acceptance-test/SKILL.md
golangci-lint run

Regression protection: if the sync fixes a protocol defect, add a test that reproduces it to prevent future regressions.

Boundaries

Do not vendor or patch third-party library source directly in this repo; changes go through the fork repo.
replace points only to the trusted org fork; do not introduce unknown third-party branches.
Upgrades must be explained in the PR: upstream commit range, risk assessment, and whether protocol behavior is affected.

Acceptance

go.mod / go.sum are consistent, go mod tidy leaves no residue
Full + integration tests pass
The tracking issue records the sync decision (sync / defer + rationale)
PR references TR-F021 / TR-F022

More from this repository

same repository

release-version

talkincode/toughradius

Review merged PRs since the last Git tag and decide whether a ToughRADIUS release is warranted. Use when Codex is asked to prepare a version release, audit unreleased changes, decide whether to publish, create a new release tag, or tag origin/main after PR review.

2026-07-08672

orchestrate-roadmap

talkincode/toughradius

Global orchestrator / dispatcher role. Activated when the user issues an "auto-delegate development / continue the roadmap / auto-delegate" command (without naming a specific subtask); runs the full loop - select task, pick SOP, dispatch, quality gates, open PR, self-iterate the roadmap.

2026-06-11672

review-pr

talkincode/toughradius

Independent review gate for auto-delegation PRs (TR-F022). Use after an orchestration round opens a PR, and as the first step of every new round to clear in-flight PRs - run an adversarial, CI-anchored review, request changes via labels + comments, and auto-merge only when the review passes and CI is green.

2026-06-11672

document-go-apis

talkincode/toughradius

Standard-library-style Go API documentation and comment conventions (TR-F024). Use when adding or changing exported Go identifiers, writing package comments, or backfilling godoc on a package so it reads like the Go standard library.

2026-06-09672

add-acceptance-test

talkincode/toughradius

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.

2026-06-08672

add-adminapi-endpoint

talkincode/toughradius

Add a group of Admin REST endpoints in the management backend (TR-F012). Use when a feature needs management APIs such as create/read/update/delete.

2026-06-08672

name	sync-upstream-radius
description	Track and sync the upstream layeh.com/radius library to the org fork talkincode/radius (TR-F021/TR-F022). Use when a check finds new upstream commits, a protocol-library defect is suspected, or for routine dependency maintenance.

Skill: Track & Sync the Upstream RADIUS Library

Feature IDs: TR-F021 / TR-F022 | Milestone: M7

Background

Core protocol library: layeh.com/radius (original repo https://github.com/layeh/radius).
Org fork: github.com/talkincode/radius (https://github.com/talkincode/radius).
Wiring: in go.mod
```
require layeh.com/radius v0.0.0-<pseudo>
replace layeh.com/radius => github.com/talkincode/radius v<tag>
```
i.e. the build actually uses the fork, while the layeh.com/radius import path stays unchanged.

When to use

Routine (weekly recommended) manual check of whether upstream layeh/radius has new commits.
When a protocol codec / attribute-handling / security defect is found or suspected.
During routine dependency maintenance.

Steps

Confirm the currently pinned version
```
grep -E "layeh.com/radius|talkincode/radius" go.mod
```
Record the fork tag the replace points to, and the upstream commit short SHA in the require pseudo-version.
Diff against upstream
- Original repo layeh/radius: review new commits since the pinned commit, e.g. via GitHub compare: https://github.com/layeh/radius/compare/<pinned_sha>...master, or git log <pinned_sha>.. in an upstream clone.
- Focus on: security fixes, attribute codec correctness, EAP / VSA / packet-parsing changes.
Assess the sync
- If an upstream fix is important and the fork lacks it: merge/cherry-pick it into the fork (talkincode/radius) and cut a new tag.
- Update this repo's go.mod replace to the new tag and run go mod tidy.
- If the fix does not affect this project's usage, record the "assessed, sync deferred" rationale (reply in the tracking issue).

Verify

go build ./...
go test ./...
go test -tags=integration -count=1 ./test/integration/...   # needs Postgres, see ../add-acceptance-test/SKILL.md
golangci-lint run

Regression protection: if the sync fixes a protocol defect, add a test that reproduces it to prevent future regressions.

Boundaries

Do not vendor or patch third-party library source directly in this repo; changes go through the fork repo.
replace points only to the trusted org fork; do not introduce unknown third-party branches.
Upgrades must be explained in the PR: upstream commit range, risk assessment, and whether protocol behavior is affected.

Acceptance

go.mod / go.sum are consistent, go mod tidy leaves no residue
Full + integration tests pass
The tracking issue records the sync decision (sync / defer + rationale)
PR references TR-F021 / TR-F022