菜单
Publish a news entry to the amiport site. Appends to site/data/news.json, validates, deploys via site-manager, and clears the activity cache. Use when announcing a release, project update, milestone, or behind-the-scenes note.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Capture a lesson learned from a porting session and route it to the right enforcement mechanism. Use when a bug, mistake, or process failure occurs that should be prevented in future sessions.
Analyze C source code for Amiga portability issues. Scans headers, system calls, and language features to produce a structured porting report. Use when starting a new port or evaluating whether a project can be ported.
Transform C source code for Amiga compatibility. Replaces POSIX calls with Amiga equivalents or posix-shim wrappers. Use after analyze-source has identified issues.
Dispatch multiple ports from the catalog in parallel using specialized agents. Runs the same pipeline stages as /port-project but overlaps them across ports for ~3x throughput.
Port an entire C project to AmigaOS. Runs the full pipeline — analyze, transform, build, test, package. Use to port a new project from scratch.
Show comprehensive status of a single port — build, tests, reviews, catalog, site data, documentation
| name | post-news |
| description | Publish a news entry to the amiport site. Appends to site/data/news.json, validates, deploys via site-manager, and clears the activity cache. Use when announcing a release, project update, milestone, or behind-the-scenes note. |
| user_invocable | true |
Adds a news entry to site/data/news.json, deploys the site, and refreshes caches so the post appears on the homepage activity feed, the News archive page (news.html), and the RSS feed (feed.php).
/post-news # Interactive — prompt for title + body
/post-news <title> # Title on command line, prompt for body
If the user has not provided a title + body in the current conversation, ask for:
site/js/news.js:
[label](url) — links (http(s) or site-relative only)**bold**`code`["release", "amigit"]/news.html#<id>)Do not fabricate any of these. Ask.
site/data/news.json (JSON array). If missing or malformed, stop and report — do not overwrite.{
"id": "<YYYY-MM-DD>-<slug>",
"date": "<YYYY-MM-DDTHH:MM:SSZ>",
"title": "<title>",
"body": "<body>",
"tags": ["..."],
"url": "<optional canonical url>"
}
id — <today>-<kebab-case slug> derived from the title. Slug max 40 chars. Must be unique within the file — if it collides, append -2, -3, etc.date — current UTC timestamp (ISO 8601, Z suffix).title — ASCII only. Reject em-dashes and smart quotes — replace with -- and straight quotes before writing. amiga.html and feed.php consume this.body — ASCII only, same rule. Preserve paragraph breaks.news.js re-sorts by date on render).site/data/news.json back. Validate that python3 -c "import json; json.load(open('site/data/news.json'))" still parses.site-manager agent with this prompt:
"Deploy the site to Dreamhost. A new news entry has been added to
site/data/news.json. Run the standard rsync deploy, then clear the activity cache on the server (/tmp/amiport-activity-cache.json), then verify/feed.phpand/news.htmlreturn 200."
https://amiport.platesteel.net/news.htmlhttps://amiport.platesteel.net/feed.phphttps://amiport.platesteel.net/api/v1/activity.phptitle and body. Reject em-dash (U+2014), smart quotes (U+2018-201D), arrows (U+2192). Replace with ASCII equivalents (--, ', ", ->) before writing. This is the same rule as .claude/rules/aminet-publishing.md and .claude/rules/amiga-coding.md — amiga.html renders news too and ARexx tools may consume the feed.news.json. Grep for the slug before writing.python3 -c "import json; json.load(...)" fails, restore from the backup the skill writes first (site/data/news.json.bak).news.json manually through Edit when this skill exists — use the skill so validation + deploy + cache clear happen atomically.news.json is not in the hook, so local and server can drift if you commit first and deploy later.data/catalog.json and site/data/packages/*.json)..claude/agents/site-manager.md — handles the actual deploy. Also documents the "The data/ Proxy Pattern" section that explains why site/data/news.json is served to browsers via site/api/v1/news.php (the .htaccess blocks direct data/ access). Any new public data file under site/data/ MUST have a corresponding api/v1/ proxy endpoint..claude/rules/catalog-sync.md — activity cache file location and why it must be clearedsite/js/news.js — how body markdown-lite is renderedsite/api/v1/news.php — the proxy endpoint that browsers fetch (do NOT change news.js to fetch data/news.json directly — it will 403)site/feed.php — how news items appear in RSS alongside packages (reads data/news.json server-side, bypasses the proxy)