nseng.ai
Official@nseng-ai
Keeping the clankers in check: Nonslop Engineering for AI
Agent Skills by nseng.ai
Showing 77 vetted skills indexed across 1 GitHub repositories.
research
Investigates questions against primary sources and writes cited findings to Markdown files.
domain-modeling
Build and maintain a project domain glossary and architectural decision records.
wayfinder
Plan large multi-session efforts as decision-ticket maps on an issue tracker.
writing-for-agents
Guides writing and structuring documents that agents consume, including skills and AGENTS.md files.
wait-what
Requests the assistant re-explain its last message in simplified technical English.
diagnosing-bugs
Diagnose hard bugs and performance regressions through a structured six-phase feedback-loop workflow.
improve-codebase-architecture
Scan a codebase for module deepening opportunities and present them as a visual HTML report.
codebase-design
Designs deep modules with small interfaces, clean seams, and testable adapters.
prototype
Build throwaway HTML or UI prototypes to answer design questions about logic or layout.
pocock-resolving-merge-conflicts
Resolves in-progress git merge and rebase conflicts by tracing original change intent.
grill-with-docs
Interviews users to sharpen plans and designs while generating ADRs and glossary documents.
pocock-review
Reviews a git diff against coding standards and the originating spec using parallel sub-agents.
unslop
Rewrites text to remove AI writing patterns and restore natural human voice.
tdd
Guides test-driven development through red-green cycles with seam-based test design.
grill-me
Runs a relentless interview session to sharpen a plan or design.
thermo-nuclear-code-quality-review
Reviews branch diffs for structural regressions, file-size growth, and spaghetti-condition complexity.
grilling
Interviews the user in structured question rounds to stress-test plans and decisions.
fdt-refactor-mock-to-fake
Refactor unittest.mock-based tests into gateway-injected fakes with pre-canned responses.
brmem
Stores and retrieves branch-scoped text entries in Git via the brmem CLI.
slots
Manage numbered git worktree pools with foreach execution and trunk fast-forwarding.
pr-address
Downloads GitHub PR feedback and triages review threads through disposition planning and confirmed resolution.
ns-gs-restack-resolve
Drives the ns gs restack-resolve conflict-resolution workflow through sequential subagent dispatch.
branch-context-from-plan
Creates an implementation branch from a saved plan and attaches it as branch context.
branch-context
Manages saved implementation plans attached to git branches via Branch Memory.
Frequently Asked Questions About nseng.ai
FAQPage SchemaWhat tasks can I accomplish with nseng.ai's skills?▼
The 77 skills cover diagnosing bugs, test-driven development, strict code-quality reviews, resolving git merge and restack conflicts, splitting large PRs into Graphite stacks, drafting ADRs and domain models, syncing changelogs, and stripping AI stylistic tells from prose.
Who are these skills designed for?▼
Software engineers running AI coding agents on real repositories, especially teams using Graphite stacked PRs, GitHub CLI, TypeScript with pnpm/Vitest, and trunk-based development who want enforced review discipline, planning rigor, and durable cross-session context.
How do I install and run these skills?▼
Skills are managed with the `npx skills` command to add, edit, remove, or list them, using nested `skills/<disposition>/.../<name>/` or flat `.agents/skills/` layouts. Many skills invoke via explicit slash commands like `/ns:handoff:create` or trigger on natural-language phrases.
What prerequisites and dependencies do the skills require?▼
Depending on the skill: git, the GitHub CLI (gh), Graphite (gt), the `ns` CLI family (slot, flow, handoff, objective), `brmem` for branch memory, plus project toolchains such as Bun, pnpm, Vitest, dprint, just, and uv for test execution.
Are nseng.ai's skills free to use?▼
The skills are published as public repositories on GitHub under the nseng-ai organization with no stated cost. The manifest does not specify an explicit license, so users should check the individual repository for licensing terms before redistribution.