Skip to main content
GitHub 저장소

agentic-engineering

agentic-engineering에는 pulsemcp에서 수집한 skills 7개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
7
Stars
0
업데이트
2026-03-10
Forks
1
직업 범위
직업 카테고리 3개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

adjust-claude-mcp-json
소프트웨어 개발자

Generate or update a Claude Code .mcp.json file from the project's mcp-servers/mcp.json. Use when the user wants to configure Claude Code's MCP servers from the trusted server set.

2026-03-10
create-mcp-json
소프트웨어 개발자

Create an mcp.json client configuration from a server.json. Use when the user wants to generate a ready-to-use MCP client config for connecting to an MCP server.

2026-03-10
create-server-json
소프트웨어 개발자

Create a valid MCP Registry server.json file for an MCP server. Use when the user wants to generate, scaffold, or write a server.json for any MCP server project.

2026-03-10
perform-release
네트워크·컴퓨터 시스템 관리자

Trigger a production release via GitHub Actions, monitor the ECS deployment, and verify the release is healthy. Use this skill when it's time to ship — after the PR is merged, CI is green, and staging has been verified. Also use it when asked to deploy, release, or ship to production.

2026-02-09
wait-for-ci
소프트웨어 품질 보증 분석가·테스터

Block until CI passes or fails on the current PR. Use this skill every time you push a commit and intend to tell the user the work is done — never present a pushed commit as complete without first confirming CI is green. Also use it when waiting on CI before merging, deploying, or moving on to the next task in a multi-step plan.

2026-02-09
initial-pr-review
소프트웨어 품질 보증 분석가·테스터

Run a structured first-pass code review on a PR. Use this skill when asked to review a PR, when opening a PR that should be sanity-checked before requesting human review, or when picking up someone else's PR to understand what changed and whether it's ready to merge.

2026-02-09
test-in-staging
소프트웨어 품질 보증 분석가·테스터

Deploy the current branch to staging and verify it works end-to-end. Use this skill after CI passes when you need to confirm changes actually work in a real environment before merging — especially for user-facing changes, API modifications, or anything that interacts with external services. Do not consider a PR "ready to merge" for non-trivial changes without a staging check.

2026-02-09