Computer Science student at Chongqing University
Building local-first safety tools, repo doctors, and delivery workflows for AI-agent-era software.
English | 简体中文
I turn fragile development workflows into small tools that are easy to run, review, and ship again. This profile is the quick map; the website is the broader portfolio and project index.
Main hub: aolingge.dev · Projects: aolingge.dev/projects · Blog RSS: blog.aolingge.dev/feed
| Area | What I build |
|---|---|
| AI-agent reliability | CLIs that check repo instructions, secrets, CI, MCP configs, run traces, and release readiness before an agent marks work as done. |
| Local automation | Repeatable scripts and workflow kits for Windows-first development, deployment checks, and safe long-running agent tasks. |
| Practical backend and delivery | Java / Spring Boot practice projects, deployment notes, and portfolio material with clear verification paths. |
| If you want to... | Start with | Why |
|---|---|---|
| Audit an AI-agent repository before launch | agent-secret-guard | Flagship safety scanner with a short first run and GitHub Action support. |
| Understand the whole release-readiness picture | agent-reliability-kit | Combines README quality, CI evidence, secrets, MCP hygiene, and release proof. |
| Debug MCP setup quickly | mcp-config-doctor | Focused local diagnosis for config paths, transports, commands, and env assumptions. |
| See the public portfolio source | open-source-portfolio | Bilingual React/Vite portfolio template wired for GitHub Pages. |
| Deploy a student or practice project | student-deploy-kit | Practical deployment recipes for frontend, Spring Boot, Docker, Nginx, and VPS work. |
| Label | Meaning | Current examples |
|---|---|---|
| Core tool | Polished public project with a clear user, command, docs, and verification path. | agent-secret-guard, agent-reliability-kit, mcp-config-doctor |
| Building block | Small CLI or check that solves one problem and may later merge into a larger kit. | repo-release-proof, readme-demo-link-check, prompt-yaml-lint |
| Learning sample | Project kept mainly for portfolio evidence, architecture practice, or deployment notes. | student-deploy-kit, express-locker-backend, job-backend |
| Content base | Knowledge or resource repository where navigation and contribution rules matter most. | deutsch-lernen, indie-hacker-tools-plus |
| Project | Use it for | First command |
|---|---|---|
| agent-secret-guard | Fast safety scan for AI-agent repos, MCP configs, browser profile paths, and risky GitHub Actions permissions. | npx agent-secret-guard scan . --fail-on high |
| mcp-config-doctor | Diagnose MCP config files before an AI client fails to connect. | npx mcp-config-doctor --config mcp.json |
| agent-reliability-kit | One report for AI-agent repo readiness, README quality, CI, secrets, MCP, n8n, and release risk. | npx agent-reliability-kit scan . |
| repo-release-proof | Check whether release notes prove what changed, how it was verified, and where it was published. | npx github:aolingge/repo-release-proof --path RELEASE.md |
| Project | Why it matters |
|---|---|
| mcp-config-doctor | Local diagnosis for MCP config paths, transports, commands, and environment assumptions before an AI client fails. |
| agent-reliability-kit | Cross-checks README quality, CI evidence, secret risk, MCP hygiene, and release proof in one readiness report. |
| repo-release-proof | Keeps release notes accountable by linking change claims to verification and publication evidence. |
| agent-symphony-kit | Local-first task files, preflight checks, gate reports, and workflow contracts for coding agents. |
| agent-run-trace-pack | Redacted, reviewable trace packs for agent and shell runs. |
| open-source-portfolio | A GitHub Pages portfolio template focused on proof, deployment, and service clarity. |
| student-deploy-kit | Beginner-friendly deployment material for Nginx, Spring Boot, frontend apps, Docker, VPS security, and troubleshooting. |
| vps-deploy-doctor | Read-only VPS diagnostics for Nginx, systemd, ports, Docker, firewall, disk, memory, and logs. |
Smaller CLI repositories stay public when they are useful as focused examples, but the profile highlights the sharper entry points above so visitors do not have to choose between dozens of similar checks.
| Surface | Purpose |
|---|---|
| GitHub profile | Fast identity, selected tools, and contact path. |
| aolingge.dev | Portfolio, project index, and longer-form notes. |
| open-source-portfolio | The React/Vite source for the bilingual portfolio page. |
| maintenance digest | Weekly repository-health issue for profile maintenance, Dependabot visibility, and security-alert awareness. |
I take a small number of focused launch-readiness audits for public or shareable AI-agent, MCP, GitHub Actions, and local automation repositories.
| Service | Deliverable |
|---|---|
| AI Agent Repo Safety Audit | A 24-hour Markdown risk summary covering agent instructions, MCP args, local credential paths, browser profile exposure, CI permissions, and practical fixes. |
| Fix PR | A scoped pull request that moves risky examples toward safer defaults after an audit. |
| Local automation hardening | A review of repo docs, workflows, and scripts before public release or handoff. |
Send a public repository link by email or GitHub. Do not send production secrets, cookies, private keys, or live credentials.
TypeScript, JavaScript, Node.js, Python, Java, Spring Boot, GitHub Actions, PowerShell.
- Make the first run boring: short commands, clear defaults, and concrete output.
- Keep reports local-first and careful around secrets, browser profiles, and account material.
- Treat documentation as part of the product, not a cleanup step.
- Prefer small, inspectable tools that compose into a stronger workflow.
Clean workflows. Local-first safety. Reusable delivery.
Chongqing City · Chongqing University · open-source notes, tools, and experiments