← all publishers

amkisko

@amkisko source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Rfc Process · amkisko bundle

   Write, number, and advance RFCs in the house shape used across amkisko libraries. Use when adding an RFC, claiming an id, copying the template, mapping status, flattening an RFC tree, or aligning a repo to this process.
   0
   installs
2. ▌
   Claims Audit · amkisko bundle

   Inventory and verify checkable claims, quotations, dates, statistics, research summaries, causal statements, and citations in docs or prose. Use for factual review, source audits, citation checks, or verification when text relies on external events, scholarship, technical behavior, law, policy, or other verifiable assertions.
   0
   installs
3. ▌
   Changelog Update · amkisko bundle

   Update CHANGELOG.md and usr/docs/changelogs in amkisko house style. Use when editing changelogs, preparing releases, or syncing engineering notes into product-facing release text.
   0
   installs
4. ▌
   Dependency Audit · amkisko bundle

   Select, alter, and audit third-party dependencies with advisory scans, target-scoped vulnerability assessments, and deep recon/OSINT. Use when adding, replacing, or removing packages; when asked to audit, review, or harden dependency graphs, lockfiles, or manifests; or when ordinary work surfaces suspicious package behavior, an advisory, a scanner match, or a plausible vulnerability or exploitation signal involving a package. Includes freshness lag (libyears or equivalent).
   0
   installs
5. ▌
   Engineering Audit · amkisko bundle

   Audit code with an evidence-first, pipeline-aware review format. Use for engineering audits, systems reviews, hot-path and Big-O analysis, pipeline inspection, resource and budget, trace and identification, product-surface, privacy, performance, observability, security, contract, and learned-systems reviews. Modes skip when they do not apply. Language- and framework-agnostic. When the system has external services, devices, operators, or physical actuators, also run boundary and control mode. For every executable tree, also run resource and budget mode and trace and identification mode. Skip those two when the tree never becomes executed bytes.
   0
   installs
6. ▌
   Public Surface Recon · amkisko bundle

   Blackbox public web recon — HTTP, archives, public repos only. Never local filesystem evidence.
   0
   installs
7. ▌
   Operational Signal Intake · amkisko bundle

   Triage live service evidence from alerts, error groups, monitors, traces, profiles, metrics, logs, probes, deployment changes, and user reports. Use to establish observed impact, test reliability and security hypotheses such as resource exhaustion or abuse, correlate the minimum useful evidence, record confidence and gaps, and route confirmed work. Do not use to install telemetry, redesign monitoring, conduct a full engineering or vulnerability audit, or mutate production.
   0
   installs